Boost C++ Libraries: Ticket #13420: small_vector - invalid move constructor/move assignment for size < N

version changed

anonymous — Thu, 25 Jan 2018 05:00:32 GMT

version Boost 1.65.0 → Boost 1.66.0

Ion Gaztañaga — Sat, 27 Jan 2018 21:23:16 GMT

There is not requirement that a move constructor or assignment must empty the source. Source must be in a consistent but unspecified state.

Antervis — Sat, 27 Jan 2018 22:42:04 GMT

Replying to Ion Gaztañaga:

There is not requirement that a move constructor or assignment must empty the source. Source must be in a consistent but unspecified state.

even though current behavior is standard-conforming, it is certainly inconsistent both with standard containers (which are empty after being moved out) and with itself (moved out state depends on initial state). I personally don't see a reason for this behavior to be an intended design choice and I suggest it to be changed

status changed; resolution set

Ion Gaztañaga — Sun, 28 Jan 2018 21:45:37 GMT

status new → closed
resolution → invalid

I've reviewed some STL implementations, specifically operator=(vector&&source), the case when the allocator shall not be propagated allocator_traits::propagate_on_container_move_assignment or allocators don't compare equal. In those cases memory can't be stolen from the source container and elements are move constructed from source to destination.

libstdc++ clears the source vector
libc++ and msvc don't clear the source vector (size is unchanged)

The standard says for operator=(vector&&) (the move constructor always transfers the allocator and does not support different storage types for source and destination like small_vector) that *this shall have the same value "source" had but no guarantee about the state of "source".

So I'm reluctant to change the implementation to clear the source. If many users find this annoying then we will reopen the issue. Thanks for the report.