Why does shared_ptr have a move constructor

Question

In C++11 std::shared_ptr has a move constructor and move assignment operator.

Is there a reason why this is needed, ie would any programs using it behave differently if there were only the copy constructor and assignment operators?

It seems that the only effect of it is that the extra increment and later decrement of the reference counter is avoided.

Answer 1

Copying a shared pointer is very expensive, since the internal reference counts need to be modified atomically and with the correct memory ordering, which may incur bus locks and fences. (Recall that multiple threads may have be copying their own, local shared pointers that own the same object.) When you actually want to transfer ownership away from one and into another object, none of this is needed, and moving is superior.