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.9 [futures] Status: Resolved Submitter: Detlef Vollmann Opened: 2009-10-22 Last modified: 2016-02-10
Priority: Not Prioritized
View all other issues in [futures].
View all issues with Resolved status.
With the addition of async(), a future might be associated with a function that is not running in a different thread but is stored to by run synchronously on the get() call. It's not clear what the wait() functions should do in this case.
Throw an exception.
2010 Pittsburgh: Moved to
NAD Editorial. Rationale added below.
Solved by N3058.