News for hackers. Stuff that matters.
Re:C++: Return value optimization vs. std::move by ExpiredLink on Monday July 20, 2015 @12:15PM (#9917037)
RVO is flawed because the compiler may(!) elide function calls. The compiler cannot know if those function calls are semantically superfluous or not.

'move' is flawed because if blurs the object id == object address equality inherited from C.

Both, RVO and 'move' are workarounds for language deficits - workarounds gone wrong.

Re:C++: Return value optimization vs. std::move by TheCoelacanth on Monday July 20, 2015 @02:42PM (#9918090)
A copy constructor that cannot be elided is a broken copy constructor.
Re:C++: Return value optimization vs. std::move by ExpiredLink on Monday July 20, 2015 @05:49PM (#9919337)
This may be true for simple structs but is definitely wrong as a general statement. Compilers cannot anticipate semantics.
Re:C++: Return value optimization vs. std::move by TheCoelacanth on Tuesday July 21, 2015 @09:56AM (#9922256)
It is true for all copy constructors in C++ since the standard allows compilers to perform copy elision.