[PATCH] [clang-tidy] Add a checker for swapped literal arguments.
djasper at google.com
Thu Jul 10 09:40:35 PDT 2014
I think for this (and probably many future clang-tidy checks), the answer
"Does this make sense as a compiler warning?" is always: YES. However,
clang-tidy enables us to quickly develop and tune an implementation using
AST matchers, not worrying about slowing down the compiler and testing it
on a larger codebase in order establish whether a check/warning provides
sufficient benefit and even let users play around with it to get more
feedback. So, I see clang-tidy as a prototyping platform and good checks
will be turned into compiler warnings. At some stage we might want to think
about how we can simplify that process, i.e. how we can make porting a
clang-tidy check into a compiler warning easier, but IMO that stage isn't
On Thu, Jul 10, 2014 at 5:38 PM, Nico Weber <thakis at chromium.org> wrote:
> Wouldn't this make sense as a regular warning?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the cfe-commits