Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(1411)

Unified Diff: cc/resources/picture_layer_tiling_set.cc

Issue 544863008: cc: Change TODO into comment. (Closed) Base URL: https://chromium.googlesource.com/chromium/src.git@master
Patch Set: Created 6 years, 3 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
« no previous file with comments | « no previous file | no next file » | no next file with comments »
Expand Comments ('e') | Collapse Comments ('c') | Show Comments Hide Comments ('s')
Index: cc/resources/picture_layer_tiling_set.cc
diff --git a/cc/resources/picture_layer_tiling_set.cc b/cc/resources/picture_layer_tiling_set.cc
index c79923539fe12d4131c88a544d90d6b7c841646a..d6594dfd0dab8b20607b5329414f0adc94c0a6eb 100644
--- a/cc/resources/picture_layer_tiling_set.cc
+++ b/cc/resources/picture_layer_tiling_set.cc
@@ -334,8 +334,9 @@ size_t PictureLayerTilingSet::GPUMemoryUsageInBytes() const {
PictureLayerTilingSet::TilingRange PictureLayerTilingSet::GetTilingRange(
TilingRangeType type) const {
- // TODO(reveman): Compute these ranges only when the tiling set has changed
- // instead of each time GetTilingRange() is called.
+ // Doesn't seem to be the case right now but if it ever becomes a performance
+ // problem to compute these ranges each time this function is called, we can
+ // compute them only when the tiling set has changed instead.
TilingRange high_res_range(0, 0);
TilingRange low_res_range(tilings_.size(), tilings_.size());
for (size_t i = 0; i < tilings_.size(); ++i) {
« no previous file with comments | « no previous file | no next file » | no next file with comments »

Powered by Google App Engine
This is Rietveld 408576698