Jan Piotrowicz

This issue is a copy of one that already has more votes: https://github.com/lefticus/cpp_weekly/issues/52

"Never write std::move() on a const object, it is silently transformed into a copy (see Item 23 in [Meyers15])" This is not true. `std::move` only performs a cast to rvalue,...

Maybe the line could be changed to something like: "use `std::move` on const object only if there exists a `const&&` overload of the function you are passing the object to"?...

That's not the point. This document is a source of C++ knowledge and if you include false information here it will spread. Compiler vendors for example create warnings based on...

@jwakely So maybe if `const&&` are so rare we should not say anything about them? Just an option... I think either not saying anything or going into too much detail...

Is there a chance to change the wording such that it permitts correct use? Microsoft changed their error description [C26478,](https://learn.microsoft.com/en-us/cpp/code-quality/c26478?view=msvc-170#remarks) but (I suppose to be conforming to the these guidelines)...