Created on 2013-04-23.00:00:00 last changed 127 months ago
Proposed resolution:
Change to [container.requirements.general] p13:
-13- All of the containers defined in this Clause and in (21.4) except array and dynarray meet the additional requirements of an allocator-aware container, as described in Table 99.
[ 2014-06-06 pre-Rapperswill ]
This issue has been reopened as arrays-ts.
[ 2013-09 Chicago ]
Move to Deferred. This feature will ship after C++14 and should be revisited then.
Addresses: arrays.ts
[container.requirements.general] p3 says:
"All of the containers defined in this Clause and in (21.4) except array meet the additional requirements of an allocator-aware container, as described in Table 99."
Is this true of dynarray? I believe the answer must be no because dynarray has no allocator_type, and morally should be no, so that operations are defined in terms of std::allocator<T>, which p13 says doesn't actually need to be used (which allows the elements to be default-initialized as is intended, rather than "default-inserted into the container" using an allocator.)
The requirement that "each element is constructed with uses-allocator construction" provides roughly equivalent behaviour to the "CopyInsertable into X" requirements for allocator-aware containers, allowing an allocator to control construction of the dynarray elements.History | |||
---|---|---|---|
Date | User | Action | Args |
2014-06-06 21:18:30 | admin | set | messages: + msg6990 |
2014-06-06 21:18:30 | admin | set | status: deferred -> open |
2013-09-26 18:26:05 | admin | set | messages: + msg6636 |
2013-09-26 18:26:05 | admin | set | status: new -> deferred |
2013-05-20 17:45:50 | admin | set | messages: + msg6520 |
2013-04-23 00:00:00 | admin | create |