================
@@ -0,0 +1,48 @@
+.. title:: clang-tidy - performance-lost-std-move
+
+performance-lost-std-move
+=========================
+
+Warns if copy constructor is used instead of ``std::move()`` and suggests a
fix.
+It honours cycles, lambdas, and unspecified call order in compound expressions.
+
+.. code-block:: c++
+
+ void f(X);
+
+ void g(X x) {
+ f(x); // warning: Could be std::move() [performance-lost-std-move]
+ }
+
+It finds the last local variable usage, and if it is a copy, emits a warning.
+The check is based on pure AST matching and doesn't take into account any
+data flow information. Thus, it doesn't catch assign-after-copy cases.
+
+Also it does notice variable references "behind the scenes":
+
+.. code-block:: c++
+
+ void f(X);
+
+ void g(X x) {
+ auto &y = x;
+ f(x); // does not emit a warning
+ y.f(); // because x is still used via y
+ }
+
+If you want to ignore assigns to reference variables, set :option: `StrictMode`
----------------
EugeneZelenko wrote:
```suggestion
If you want to ignore assigns to reference variables, set :option:`StrictMode`
```
This is statement. See `:program:` in `clang-tools-extra/docs/ReleaseNotes.rst`
as example.
https://github.com/llvm/llvm-project/pull/139525
_______________________________________________
cfe-commits mailing list
[email protected]
https://lists.llvm.org/cgi-bin/mailman/listinfo/cfe-commits
