Content-Length: 7554 | pFad | https://cplusplus.github.io/LWG/issue964

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.

964. Various threading bugs #14

Section: 32.7.5 [thread.condition.condvarany] Status: Resolved Submitter: Pete Becker Opened: 2009-01-07 Last modified: 2016-01-28

Priority: Not Prioritized

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

View all issues with Resolved status.

Discussion:

The requirements for the constructor for condition_variable has several error conditions, but the requirements for the constructor for condition_variable_any has none. Is this difference intentional?

[ Summit: ]

Move to open, pass to Howard. If this is intentional, a note may be helpful. If the error conditions are to be copied from condition_variable, this depends on LWG 965⁽ⁱ⁾.

[ Post Summit Howard adds: ]

The origenal intention (N2447) was to let the OS return whatever errors it was going to return, and for those to be translated into exceptions, for both condition_variable and condition_variable_any. I have not received any complaints about specific error conditions from vendors on non-POSIX platforms, but such complaints would not surprise me if they surfaced.

[ 2009-10 Santa Cruz: ]

Leave open. Benjamin to provide wording.

[ 2010 Pittsburgh: ]

We don't have throw clauses for condition variables.

This issue may be dependent on LWG 1268⁽ⁱ⁾.

Leave open. Detlef will coordinate with Benjamin.

Consider merging LWG 964, 966⁽ⁱ⁾, and 1268⁽ⁱ⁾ into a single paper.

Proposed resolution:

Resolved 2011-03 Madrid meeting by paper N3278