What optimization does move semantics provide if we already have RVO?

Question

As far as I understand one of the purposes of adding move semantics is to optimize code by calling special constructor for copying \"temporary\" objects. For example, in th

Answer 1

Your posted example only takes const lvalue references and so explicitly cannot have move semantics applied to it, as there is not a single rvalue reference in there. How can move semantics make your code faster when you implemented a type without rvalue references?

In addition, your code is already covered by RVO and NRVO. Move semantics apply to far, far more situations than those two do.