Eugene.Zelenko added a comment. In https://reviews.llvm.org/D40937#947658, @szepet wrote:
> Other note: If somebody would came up with an approach which can benefit from > the symbolic execution, these solutions could still live happily in the > different tools eg. UseAfterMove (tidy) and MisusedMovedObjectChecker > (analyzer). I'm more concerned with path sensitivity and reporting. From my point of view UseAfterMove also belongs to Analyzer realm. Actually //bugprone// module may be better choice then //misc//. ================ Comment at: docs/ReleaseNotes.rst:63 + + The check finds loops where none of the condition variables are updated in the + body. ---------------- Please remove //The check//. See other checks release notes and documentation as style examples. Please rebase from trunk, since I sorted Clang-tidy notes recently, so just prefer to avoid this task in future :-) https://reviews.llvm.org/D40937 _______________________________________________ cfe-commits mailing list cfe-commits@lists.llvm.org http://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
