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.5.4 [thread.mutex.requirements] Status: Resolved Submitter: INCITS Opened: 2010-08-25 Last modified: 2016-02-10
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.
try_lock does not provide a guarantee of forward progress because it is allowed to spuriously fail.
[ Resolution proposed by ballot comment: ]
The standard mutex types must not fail spuriously in try_lock. See n3141 page 205 - Appendix 1 - Additional Details
[ 2010-11-01 Daniel comments: ]
Paper n3152 addresses this issue.
Resolved by n3209.