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.
Section: 32.6.4 [thread.mutex.requirements] Status: Resolved Submitter: Switzerland Opened: 2010-08-25 Last modified: 2016-01-28
Priority: Not Prioritized
View other active issues in [thread.mutex.requirements].
View all other issues in [thread.mutex.requirements].
View all issues with Resolved status.
Discussion:
Addresses CH-27
The mutex requirements force try_lock to be
noexcept(true). However, where they are used by the
generic algorithms, those relax this requirement and say
that try_lock may throw. This means the requirement is
too stringent, also a non-throwing try_lock does not allow
for a diagnostic such as system_error that lock()
will give us.
[ Resolution proposed by ballot comment: ]
delete p18, adjust 30.4.4 p1 and p4 accordingly
[ 2010-11-01 Daniel comments: ]
Accepting n3130 would solve this issue.
Proposed resolution:
Resolved by n3197.