Difference between revisions of "cpp/named req/Erasable"
m (T. Canens moved page cpp/concept/Erasable to cpp/named req/Erasable without leaving a redirect: Text replace - "cpp/concept" to "cpp/named req") |
m (Text replace - "cpp/concept" to "cpp/named req") |
||
| Line 1: | Line 1: | ||
| − | {{cpp/ | + | {{cpp/named req/title|Erasable}} |
| − | {{cpp/ | + | {{cpp/named req/navbar}} |
Specifies that an object of the type can be destroyed by a given {{concept|Allocator}}. | Specifies that an object of the type can be destroyed by a given {{concept|Allocator}}. | ||
Revision as of 13:59, 15 June 2018
Specifies that an object of the type can be destroyed by a given Template:concept.
Requirements
The type T is Template:concept from the Template:concept X whose value_type is identical to T if, given
A
|
an allocator type |
m
|
an lvalue of type A
|
p
|
the pointer of type T* prepared by the container
|
where X::allocator_type is identical to std::allocator_traits<A>::rebind_alloc<T>,
the following expression is well-formed:
std::allocator_traits<A>::destroy(m, p);
If X is not allocator-aware, 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.
Notes
All standard library containers require that their element type satisfies Erasable.
With the default allocator, this requirement is equivalent to the validity of p->~T(), which accepts class types with accessible destructors and all scalar types, but rejects array types, function types, reference types, and void.
See Also
| Template:concept | |
| Template:concept | |
| Template:concept | |
| Template:concept |
