aaron.ballman accepted this revision.
aaron.ballman added a comment.
This revision is now accepted and ready to land.
In https://reviews.llvm.org/D43867#1021985, @alexfh wrote:
> In https://reviews.llvm.org/D43867#1021956, @aaron.ballman wrote:
>
> > When we do this sort of move, do we want to ke
alexfh added a comment.
In https://reviews.llvm.org/D43867#1021956, @aaron.ballman wrote:
> When we do this sort of move, do we want to keep the check under its old name
> for a deprecation period so that we are less likely to break automated
> scripts and whatnot?
I haven't done this for the
aaron.ballman added a comment.
When we do this sort of move, do we want to keep the check under its old name
for a deprecation period so that we are less likely to break automated scripts
and whatnot?
Repository:
rCTE Clang Tools Extra
https://reviews.llvm.org/D43867
alexfh updated this revision to Diff 136275.
alexfh added a comment.
- Fixed a header guard
Repository:
rCTE Clang Tools Extra
https://reviews.llvm.org/D43867
Files:
clang-tidy/bugprone/BugproneTidyModule.cpp
clang-tidy/bugprone/CMakeLists.txt
clang-tidy/bugprone/ForwardingReferenceOve
alexfh created this revision.
alexfh added reviewers: hokein, sammccall, aaron.ballman.
Herald added subscribers: mgorny, klimek.
rename_check.py {misc,bugprone}-forwarding-reference-overload
rename_check.py {misc,bugprone}-macro-repeated-side-effects
rename_check.py {misc,bugprone}-lambda-functio
