Get more consistent decisions if a statement is constant in templates

tools/clang/rewrite_to_chrome_style/tests/constants-original.cc

Index: tools/clang/rewrite_to_chrome_style/tests/constants-original.cc
diff --git a/tools/clang/rewrite_to_chrome_style/tests/constants-original.cc b/tools/clang/rewrite_to_chrome_style/tests/constants-original.cc
index 51ce017823e0e59f29486e025347aa25c2154f8f..8e067318b4fcbcebae4492df43f5f4b832427bce 100644
--- a/tools/clang/rewrite_to_chrome_style/tests/constants-original.cc
+++ b/tools/clang/rewrite_to_chrome_style/tests/constants-original.cc
@@ -33,10 +33,10 @@ class C {
     const int kFunctionConstantFromExpression = 4 + 6;
     const int kFunctionConstantFromOtherConsts =
         kFunctionConstant + kFunctionConstantFromExpression;
-    // These don't do the right thing right now, but names like this don't
-    // exist in blink (hopefully).
-    const int should_be_renamed_to_a_const = 9 - 2;
-    const int should_also_be_renamed_to_a_const =
+    // These are constants but they are hacker_case, so we just leave them as
+    // is since the author explicitly did this.
+    const int should_not_be_renamed_to_a_const = 9 - 2;
+    const int should_not_also_be_renamed_to_a_const =
         kFunctionConstant + kFunctionConstantFromOtherConsts;
     const int not_compile_time_const = kFunctionConstant + Function();
   }