Title
unique_ptr<T[], D> needs to get rid of unspecified-pointer-type
Status
resolved
Section
[unique.ptr.runtime]
Submitter
Daniel Krügler

Created on 2009-12-20.00:00:00 last changed 170 months ago

Messages

Date: 2010-10-21.18:28:33

Proposed resolution:

In [unique.ptr.runtime], class template unique_ptr<T[], D> synopsis, change as indicated:

// assignment
unique_ptr& operator=(unique_ptr&& u);
unique_ptr& operator=(unspecified-pointer-typenullptr_t);
Date: 2010-10-21.18:28:33

Rationale:

Solved by N3073.

Date: 2010-03-14.00:00:00

[ 2010-03-14 Howard adds: ]

We moved N3073 to the formal motions page in Pittsburgh which should obsolete this issue. I've moved this issue to NAD Editorial, solved by N3073.

Date: 2009-12-21.00:00:00

[ 2009-12-21 Moved to Tentatively Ready after 5 positive votes on c++std-lib. ]

Date: 2009-12-20.00:00:00

Addresses UK 211

As a response to UK 211 LWG issue 1021 has replaced the unspecified-pointer-type by nullptr_t to allow assignment of type-safe null-pointer literals in the non-array form of unique_ptr::operator=, but did not the same for the specialization for arrays of runtime length. But without this parallel change of the signature we have a status quo, where unique_ptr<T[], D> declares a member function which is completely unspecified.

History
Date User Action Args
2010-11-19 19:04:45adminsetstatus: nad editorial -> resolved
2010-10-21 18:28:33adminsetmessages: + msg1481
2010-10-21 18:28:33adminsetmessages: + msg1480
2010-10-21 18:28:33adminsetmessages: + msg1479
2010-10-21 18:28:33adminsetmessages: + msg1478
2009-12-20 00:00:00admincreate