Il 28/04/21 10:40, Edward Catmur ha scritto:
> Consider a T that is (CopyInsertable,CopyAssignable, and) MoveInsertable
> but not MoveAssignable. An implementation may choose to shuffle the
> elements along by destruct-and-move rather than copy assign.
> Invalidating everything after the insertion point gives greater
> implementation freedom.

Sorry, could you please elaborate on this a bit more? A type can't be
CopyAssignable without also being MoveAssignable:

http://eel.is/c++draft/utility.arg.requirements#tab:cpp17.copyassignable

Thank you,

-- 
Giuseppe D'Angelo | giuseppe.dangelo_at_[hidden] | Senior Software Engineer
KDAB (France) S.A.S., a KDAB Group company
Tel. France +33 (0)4 90 84 08 53, http://www.kdab.com
KDAB - The Qt, C++ and OpenGL Experts