6 Commits

Author	SHA1	Message	Date
Alexander Kornienko	621e555788	[clang-tidy] Fix linkage-related compiler errors in clang-tidy tests ... llvm-svn: 313752	2017-09-20 12:16:35 +00:00
Alexander Kornienko	f2dc6492ed	[clang-tidy] misc-move-const-arg shouldn't complain on std::move(lambda) ... llvm-svn: 303554	2017-05-22 14:30:14 +00:00
Alexander Kornienko	b48986782b	[clang-tidy] Fix misc-move-const-arg for move-only types. ... Summary: Fix misc-move-const-arg false positives on move-only types. Reviewers: sbenza Reviewed By: sbenza Subscribers: xazax.hun, cfe-commits Differential Revision: https://reviews.llvm.org/D31160 llvm-svn: 302261	2017-05-05 17:33:49 +00:00
Alexander Kornienko	eedcd9c1ea	[clang-tidy misc-move-const-arg] more specific messages + suggest alternative solution ... llvm-svn: 279666	2016-08-24 21:23:24 +00:00
Alexander Kornienko	28b34b043e	[clang-tidy] misc-move-const-arg: Detect if result of std::move() is being passed as a const ref argument ... Summary: Conceptually, this is very close to the existing functionality of misc-move-const-arg, which is why I'm adding it here and not creating a new check. For example, for a type A that is both movable and copyable, this const A a1; A a2(std::move(a1)); is not only a case where a const argument is being passed to std::move(), but the result of std::move() is also being passed as a const reference (due to overload resolution). The new check typically triggers (exclusively) in cases where people think they're dealing with a movable type, but in fact the type is not movable. Reviewers: hokein, aaron.ballman, alexfh Subscribers: aaron.ballman, cfe-commits Patch by Martin Boehme! Differential Revision: http://reviews.llvm.org/D21223 llvm-svn: 272896	2016-06-16 14:32:41 +00:00
Alexander Kornienko	900cadd3ad	[clang-tidy] Now adding correct misc-move-const-arg documentation ;] ... + brushed the code a bit and renamed the test file to match the check name llvm-svn: 267592	2016-04-26 19:33:49 +00:00