status changed; resolution set

Ion Gaztañaga — Fri, 06 Nov 2015 20:54:47 GMT

status new → closed
resolution → fixed

Thanks for the report. It's an error in the comment as self assignment is not allowed for move assignments:

http://en.cppreference.com/w/cpp/utility/move

"Also, the standard library functions called with xvalue arguments may assume the argument is the only reference to the object; if it was constructed from an lvalue with std::move, no aliasing checks are made. In particular, this means that standard library move assignment operators do not have to perform self-assignment checks"

std::vector<int> v = {2, 3, 3};
v = std::move(v); // undefined behavior

Comment changed in commit https://github.com/boostorg/container/commit/08e768f1d89289f0783b5bab9ea9f2eb0753ed70

Boost C++ Libraries: Ticket #11786: Shouldn't boost::container::vector handle self-move-assignment?

status changed; resolution set