Detailed Description

A joint allocator does not propagate on assignment and it is not allowed to use the regular copy/move constructor of allocator aware containers, instead it needs the copy/move constructor with allocator.

Note

This is required because the container constructor will end up copying/moving the allocator. But this is not allowed as you need the allocator with the correct joined memory. Copying can be customized (i.e. forbidden), but sadly not move, so keep that in mind.