The word "selector" is somewhat redundant redundantly used in SelectorChecker.
Created attachment 181837 [details] Patch
Comment on attachment 181837 [details] Patch Attachment 181837 [details] did not pass win-ews (win): Output: http://queues.webkit.org/results/15754580
Comment on attachment 181837 [details] Patch Attachment 181837 [details] did not pass mac-ews (mac): Output: http://queues.webkit.org/results/15762353
Comment on attachment 181837 [details] Patch LGTM, not sure why it is not building on Mac.
(In reply to comment #4) > LGTM, not sure why it is not building on Mac. will fix.
It's weird. The error makes it sound like there's a macro check(X) that's defined somewhere.
/usr/include/AssertMacros.h #ifndef __ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES /* If we haven't set this yet, it defaults to on. In the next release, this will default to off. */ #define __ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES 1 #endif #if __ASSERT_MACROS_DEFINE_VERSIONS_WITHOUT_UNDERSCORES #ifndef check #define check(assertion) __Check(assertion) #endif ... Lame. Hmm, how about naming them match() instead? Might even read better.
Does really improve the naming? I admit SelectorChecker::checkSelector is a _very_ redundant (even Checker::check() is), but I like that the method name in itself is fully descriptive.
(In reply to comment #7) > > Hmm, how about naming them match() instead? Might even read better. Sounds good, going with that.
Created attachment 182262 [details] Patch for landing
Comment on attachment 182262 [details] Patch for landing Clearing flags on attachment: 182262 Committed r139406: <http://trac.webkit.org/changeset/139406>
All reviewed patches have been landed. Closing bug.