<div dir="ltr">Makes sense, thanks.</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, Jul 10, 2014 at 9:40 AM, Daniel Jasper <span dir="ltr"><<a href="mailto:djasper@google.com" target="_blank">djasper@google.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">I think for this (and probably many future clang-tidy checks), the answer<br>
"Does this make sense as a compiler warning?" is always: YES. However,<br>
clang-tidy enables us to quickly develop and tune an implementation using<br>
AST matchers, not worrying about slowing down the compiler and testing it<br>
on a larger codebase in order establish whether a check/warning provides<br>
sufficient benefit and even let users play around with it to get more<br>
feedback. So, I see clang-tidy as a prototyping platform and good checks<br>
will be turned into compiler warnings. At some stage we might want to think<br>
about how we can simplify that process, i.e. how we can make porting a<br>
clang-tidy check into a compiler warning easier, but IMO that stage isn't<br>
necessarily now.<br>
<br>
</div><a href="http://reviews.llvm.org/D4457" target="_blank">http://reviews.llvm.org/D4457</a><br>
<br>
<br>
</blockquote></div><br></div>