C++ named requirements: CopyInsertable (since C++11)
Specifies that an instance of the type can be copy-constructed in-place by a given allocator.
T is CopyInsertable into the container
value_type is identical to
T is MoveInsertable into
X, and, given
||an allocator type|
|| an lvalue of type |
|| the pointer of type |
|| expression of type (possibly const) |
X::allocator_type is identical to std::allocator_traits<A>::rebind_alloc<T>,
the following expression is well-formed:
std::allocator_traits<A>::construct(m, p, v);
And after evaluation, the value of *p is equivalent to the value of v. The value of v is unchanged.
X is not allocator-aware or is a std::basic_string specialization, the term is defined as if
A were std::allocator<T>, except that no allocator object needs to be created, and user-defined specializations of std::allocator are not instantiated.
Although it is required that customized
construct is used when constructing elements of std::basic_string until C++23, all implementations only used the default mechanism. The requirement is corrected by P1072R10 to match existing practice.