[llvm] r270997 - Apply clang-tidy's misc-move-constructor-init throughout LLVM.
Aaron Ballman via llvm-commits
llvm-commits at lists.llvm.org
Fri May 27 11:24:14 PDT 2016
On Fri, May 27, 2016 at 2:20 PM, David Blaikie <dblaikie at gmail.com> wrote:
> On Fri, May 27, 2016 at 11:15 AM, Aaron Ballman <aaron at aaronballman.com>
>> On Fri, May 27, 2016 at 2:06 PM, David Blaikie via llvm-commits
>> <llvm-commits at lists.llvm.org> wrote:
>> > Nice :)
>> > Do we have any way to integrate these checks into the developer workflow
>> > so
>> > we can avoid checking in the same mistakes tomorrow?
>> Implement the check as part of clang itself (if we think it's of
>> sufficient use),
> Well, I was hoping for potentially a way to add checks to clang - a
> clang-tidy clang plugin, for example? Or similar. (perhaps the performance
> wouldn't be good enough? Not sure) - or editor integration through
> YouCompleteMe or similar, with a checked in config of the checks we want to
> use/maintain/hold the project to.
Personally, I think that clang-tidy being a separate executable
instead of being driving by the clang driver is a huge hindrance to
adoption of these checks. I would *love* to see a way to execute
clang-tidy via clang (perhaps using -tidy as the driver option). It
seems like this could possibly be along the same lines of what you're
>> or have a bot that runs clang-tidy?
> Would seem annoying to get these sort of quick static analysis results back
> asynchronously/through bot failure compared to during development. (this one
> less so, but many are meant to find mistakes before you have to debug them)
More information about the llvm-commits