summaryrefslogtreecommitdiffstats
path: root/lldb/packages/Python/lldbsuite/test/lang/cpp
diff options
context:
space:
mode:
authorAlexander Kornienko <alexfh@google.com>2016-06-16 14:32:41 +0000
committerAlexander Kornienko <alexfh@google.com>2016-06-16 14:32:41 +0000
commit28b34b043ea282523c4f1dc1db858093ab8de7ac (patch)
tree56b77f9cff853b4222b15c9c81277f4680b7f778 /lldb/packages/Python/lldbsuite/test/lang/cpp
parent22ec97fb24a4d16f1f6b073d7cec45314758029e (diff)
downloadbcm5719-llvm-28b34b043ea282523c4f1dc1db858093ab8de7ac.tar.gz
bcm5719-llvm-28b34b043ea282523c4f1dc1db858093ab8de7ac.zip
[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
Diffstat (limited to 'lldb/packages/Python/lldbsuite/test/lang/cpp')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud