This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Pending NAD Editorial status.
Allocator requirement changes not mentioned Annex CSection: 16.4.4.6 [allocator.requirements], C.8 [diff.library] Status: Pending NAD Editorial Submitter: Nevin Liber Opened: 2012-08-14 Last modified: 2016-11-21
Priority: 3
View other active issues in [allocator.requirements].
View all other issues in [allocator.requirements].
View all issues with Pending NAD Editorial status.
Discussion:
Given that a number of things were removed from the allocator requirements (reference, const_reference,
address() in 16.4.4.6 [allocator.requirements]), it seems that these incompatible changes should be
mentioned in Annex C.8 [diff.library], more specifically in [diff.cpp03].
[ 2012-10 Portland: Move to Open ]
It was clearly pointed out by Bill during the C++11 process that our change to allocator requirements
potentially broke 3rd party user containers written to expect C++03 allocators, or rather, an
allocator written to the minimal requirements of C++11 might not be guaranteed to work with a container
written to the previous rules. This was a trade-off in making allocaters easier to write by use of
the allocator_traits framework.
This probably does merit a write-up in Annex C, and we look forward to seeing wording. Until then, the best we can do is move the issue to Open.
[2016-11-12, Issaquah]
Sat PM: JW to provide Annex C wording Status to "Pending NAD Editorial".
Proposed resolution: