12. Way objects hold allocators unclear

Section: 20.5.3.5 [allocator.requirements] Status: NAD Submitter: Angelika Langer Opened: 1998-02-23 Last modified: 2016-08-08

Priority: Not Prioritized

View other active issues in [allocator.requirements].

View all other issues in [allocator.requirements].

View all issues with NAD status.

Discussion:

I couldn't find a statement in the standard saying whether the allocator object held by a container is held as a copy of the constructor argument or whether a pointer of reference is maintained internal. There is an according statement for compare objects and how they are maintained by the associative containers, but I couldn't find anything regarding allocators.

Did I overlook it? Is it an open issue or known defect? Or is it deliberately left unspecified?

Rationale:

Not a defect. The LWG believes that the Standard is already clear.  See 26.2 [container.requirements], paragraph 8.