This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of NAD status.

### 1223. condition_variable_any lock matching?

Section: 32.6.5 [thread.condition.condvarany] Status: NAD Submitter: Jeffrey Yasskin Opened: 2009-09-30 Last modified: 2016-01-28

Priority: Not Prioritized

View all other issues in [thread.condition.condvarany].

View all issues with NAD status.

Discussion:

For `condition_variable_any`, must all lock arguments to concurrent wait calls "match" in some way, similar to the requirement in 32.6.4 [thread.condition.condvar] that `lock.mutex()` returns the same value for each of the lock arguments supplied by all concurrently waiting threads (via `wait` or `timed_wait`)?

[ 2010-02-12 Moved to Tentatively NAD after 5 positive votes on c++std-lib. Rationale added below. ]

Rationale:

The rationale is that it doesn't matter, and you can't check: the lock types may be different, or the same and user-defined, so the implementation must provide internal synchronization anyway.

Proposed resolution: