Title
[fund.ts] shared_ptr<array>'s constructor from unique_ptr should be constrained
Status
open
Section
[memory.smartptr.shared.const]
Submitter
Jeffrey Yasskin

Created on 2014-06-16.00:00:00 last changed 81 months ago

Messages

Date: 2015-03-22.19:17:27

Proposed resolution:

This wording is relative to N4023 in regard to fundamental-ts changes.

  1. In fundamental-ts, change [mods.util.smartptr.shared.const] p34 as indicated:

    template <class Y, class D> shared_ptr(unique_ptr<Y, D>&& r);
    

    -34- RequiresRemarks: This constructor shall not participate in overload resolution unless Y* shall beis compatible with T*.

    -35- Effects: Equivalent to shared_ptr(r.release(), r.get_deleter()) when D is not a reference type, otherwise shared_ptr(r.release(), ref(r.get_deleter())).

    -36- Exception safety: If an exception is thrown, the constructor has no effect.

Date: 2015-03-22.19:17:27

[ 2015-02, Cologne ]

Unanimous consent.

Date: 2014-06-16.00:00:00

Addresses: fund.ts

The proposed resolution for LWG 2399 doesn't apply cleanly to the Fundamentals TS, but the issue is still present.

History
Date User Action Args
2017-07-30 20:10:41adminsetstatus: wp -> open
2015-05-22 18:31:21adminsetstatus: ready -> wp
2015-03-22 19:17:27adminsetmessages: + msg7249
2015-03-22 19:17:27adminsetstatus: new -> ready
2014-06-29 11:26:49adminsetmessages: + msg7081
2014-06-16 00:00:00admincreate