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.
1269. Associated state doesn't account forasync
Section: 32.10.5 [futures.state] Status: Resolved Submitter: Anthony Williams Opened: 2009-11-18 Last modified: 2016-01-28
Priority: Not Prioritized
View all other issues in [futures.state].
View all issues with Resolved status.
Discussion:
The current description of the associated state in 32.10.5 [futures.state] does not allow for futures created by an async call. The description therefore needs to be extended to cover that.
[ 2010 Pittsburgh: Moved to NAD Editorial Resolved. Rationale added below. ]
Rationale:
Solved by N3058.
Proposed resolution:
Add a new sentence to 32.10.5 [futures.state] p2:
2 This associated state consists of some state information and some (possibly not yet evaluated) result, which can be a (possibly
void) value or an exception. If the associated state was created by a call toasync(32.10.9 [futures.async]) then it may also contain a deferred function or an associatedthread.
Add an extra bullet to 32.10.5 [futures.state] p3:
The result of an associated state can be set by calling:
promise::set_value,promise::set_exception, or- packaged_task::operator() . , or
- a call to
async(32.10.9 [futures.async]).
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4