This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of Resolved status.
Section: 6.3 [fund.ts::any.class] Status: Resolved Submitter: Jonathan Wakely Opened: 2014-06-16 Last modified: 2015-10-26
Priority: Not Prioritized
View all issues with Resolved status.
The allocator-extended copy constructor for any requires an arbitrary template parameter to be available in a type-erased context where the dynamic type of the contained object is known. This is not believed to be possible in C++.If the allocator-extended copy constructor cannot be defined it questions the usefulness of the other allocator-extended constructors.
Resolved by paper N4270.