rewrite_to_chrome_style: Static const bool used for template traits not renamed. |
|||
Issue descriptionAfter a rename in WTF: $ git gs safeToCompareToEmptyOrDeleted is 42. But: $ git gs kSafeToCompareToEmptyOrDeleted| wc -l is 5. Almost all the rewritten references are inside HashTable.h itself: the various hash function helpers exposing this trait largely aren't rewritten, with the exception of StringHash.h.
,
Sep 2 2016
Ooops. I assume that it is undesirable to rename |safeToCompareToEmptyOrDeleted| (because this is a field of a type trait). I guess I've regressed this in https://codereview.chromium.org/2307643002 and https://codereview.chromium.org/2276813003 :-(
,
Sep 2 2016
safeToCompareToEmptyOrDeleted should be safe_to_compare_to_empty_or_deleted if its a type trait.
,
Jan 18 2017
I think this is better now, or at least more consistent thanks to other stuff. It appears to be always kSafeToCompareToEmptyOrDeleted now. It's not determining it is a trait tho. The only safeToCompareToEmptyOrDeleted I see are: mojo/public/cpp/bindings/lib/wtf_hash_util.h:68: static const bool safeToCompareToEmptyOrDeleted = false; mojo/public/cpp/bindings/lib/wtf_hash_util.h:80: static const bool safeToCompareToEmptyOrDeleted = false; Which I guess should be renamed as it's a traits for WTF stuff but it is not in the WTF namespace so uh hm.
,
Jan 18 2017
The whole structs mojo::internal::StructPtrHashFn and mojo::internal::InlinedStructPtrHashFn need to be rewritten. Maybe we need to whitelist these.
,
Jan 24 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/5974c5c41238e402ecf1d0918a5e629e95536eb0 commit 5974c5c41238e402ecf1d0918a5e629e95536eb0 Author: danakj <danakj@chromium.org> Date: Tue Jan 24 17:41:30 2017 Capitalize WTF-based type traits as lower_case This uses a whitelist to consistently name type traits defined for WTF structures globally throughout chromium. R=dcheng BUG= 598177 Review-Url: https://codereview.chromium.org/2649933003 Cr-Commit-Position: refs/heads/master@{#445755} [modify] https://crrev.com/5974c5c41238e402ecf1d0918a5e629e95536eb0/tools/clang/rewrite_to_chrome_style/RewriteToChromeStyle.cpp [modify] https://crrev.com/5974c5c41238e402ecf1d0918a5e629e95536eb0/tools/clang/rewrite_to_chrome_style/tests/fields-expected.cc [modify] https://crrev.com/5974c5c41238e402ecf1d0918a5e629e95536eb0/tools/clang/rewrite_to_chrome_style/tests/fields-original.cc
,
Jan 24 2017
,
Jan 25 2017
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/9c0001763fde79549c208242560bc0d9245c6441 commit 9c0001763fde79549c208242560bc0d9245c6441 Author: danakj <danakj@chromium.org> Date: Wed Jan 25 19:55:03 2017 Rename references to type traits the same as we rename the traits. R=dcheng@chromium.org BUG= 685264 , 598177 Review-Url: https://codereview.chromium.org/2655943003 Cr-Commit-Position: refs/heads/master@{#446096} [modify] https://crrev.com/9c0001763fde79549c208242560bc0d9245c6441/tools/clang/rewrite_to_chrome_style/RewriteToChromeStyle.cpp [modify] https://crrev.com/9c0001763fde79549c208242560bc0d9245c6441/tools/clang/rewrite_to_chrome_style/tests/fields-expected.cc [modify] https://crrev.com/9c0001763fde79549c208242560bc0d9245c6441/tools/clang/rewrite_to_chrome_style/tests/fields-original.cc |
|||
►
Sign in to add a comment |
|||
Comment 1 by dcheng@chromium.org
, Mar 26 2016