Title
bad_weak_ptr::what() overspecified
Status
c++17
Section
[util.smartptr.weak.bad]
Submitter
Jonathan Wakely

Created on 2014-03-27.00:00:00 last changed 90 months ago

Messages

Date: 2014-03-27.21:45:58

Proposed resolution:

This wording is relative to N3936.

  1. Edit [util.smartptr.weakptr]:

    bad_weak_ptr() noexcept;
    

    -2- Postconditions: what() returns "bad_weak_ptr"an implementation-defined NTBS.

Date: 2014-03-27.00:00:00

[ 2014-03-27 Library reflector vote ]

The issue has been identified as Tentatively Ready based on six votes in favour.

Date: 2014-03-27.00:00:00

[util.smartptr.weakptr] p2 requires bad_weak_ptr to return precisely the string "bad_weak_ptr".

There was general agreement on the reflector and at the Issaquah meeting that this is over-constrained and implementation should be free to return something more descriptive if desired.

The proposed resolution makes bad_weak_ptr consistent with other exception types such as bad_alloc and bad_cast.

If accepted, the P/R for issue 2233, which currently uses similar wording to bad_weak_ptr, could be updated appropriately.

History
Date User Action Args
2017-07-30 20:15:43adminsetstatus: wp -> c++17
2014-11-08 19:44:42adminsetstatus: voting -> wp
2014-11-04 10:26:50adminsetstatus: ready -> voting
2014-03-27 21:45:58adminsetmessages: + msg6930
2014-03-27 21:45:58adminsetstatus: new -> ready
2014-03-27 20:35:34adminsetmessages: + msg6928
2014-03-27 00:00:00admincreate