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.
noexcept judiciously throughout the librarySection: 16 [library] Status: Resolved Submitter: BSI Opened: 2010-08-25 Last modified: 2016-01-28
Priority: Not Prioritized
View other active issues in [library].
View all other issues in [library].
View all issues with Resolved status.
Discussion:
Addresses GB-63, US-80
Since the newly introduced operator noexcept makes it
easy (easier than previously) to detect whether or not a
function has been declared with the empty exception
specification (including noexcept) library functions that
cannot throw should be decorated with the empty
exception specification. Failing to do so and leaving it as a
matter of QoI would be detrimental to portability and
efficiency.
[ Resolution proposed by ballot comment ]
Review the whole library, and apply the noexcept
specification where it is appropriate.
[ 2010-10-31 Daniel comments: ]
The proposed resolution of the combination of n3155, n3156, n3157, n3167 would satisfy this request. The paper n3150 is related to this as well.
[ 2010 Batavia: ]
While the LWG expects to see further papers in this area, sufficient action was taken in Batavia to close the issue as Resolved by the listed papers.
Proposed resolution: