Title
Apply noexcept where library specification does not permit exceptions
Status
resolved
Section
[library]
Submitter
BSI

Created on 2010-08-25.00:00:00 last changed 170 months ago

Messages

Date: 2011-05-03.22:13:16

Proposed resolution:

This issue is resolved by the adoption of n3195

Date: 2010-11-29.10:49:30

[ 2010-Batavia: ]

Resolved by adopting n3149.

Date: 2010-10-31.00:00:00

[ 2010-10-31 Daniel comments: ]

The proposed resolution of n3149 would satisfy this request.

Date: 2010-10-24.22:33:31

[ Resolution proposed by ballot comment: ]

Add a noexcept exception specification on each libary API that offers an unconditional Throws: Nothing guarantee. Where the guarantee is conditional, add the appropriate noexcept(constant-expression) if an appropriate constant expression exists.

Date: 2010-11-07.14:07:22

Addresses GB-62, CH-17

Issues with efficiency and unsatisfactory semantics mean many library functions document they do not throw exceptions with a Throws: Nothing clause, but do not advertise it with an exception specification. The semantic issues are largely resolved with the new 'noexcept' specifications, and the noexcept operator means we will want to detect these guarantees programatically in order to construct programs taking advantage of the guarantee.

History
Date User Action Args
2010-11-29 10:49:30adminsetmessages: + msg5449
2010-11-18 12:46:23adminsetstatus: nad editorial -> resolved
2010-11-13 13:11:26adminsetstatus: open -> nad editorial
2010-10-31 11:48:59adminsetmessages: + msg5205
2010-10-31 11:48:59adminsetmessages: + msg5204
2010-10-24 22:33:31adminsetmessages: + msg5053
2010-10-24 10:50:39adminsetmessages: + msg4975
2010-08-25 00:00:00admincreate