Title
Associated state doesn't account for async
Status
resolved
Section
[futures.state]
Submitter
Anthony Williams

Created on 2009-11-18.00:00:00 last changed 170 months ago

Messages

Date: 2010-10-21.18:28:33

Proposed resolution:

Add a new sentence to [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 to async ([futures.async]) then it may also contain a deferred function or an associated thread.

Add an extra bullet to [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 ([futures.async]).
Date: 2010-10-21.18:28:33

Rationale:

Solved by N3058.

Date: 2010-12-05.00:09:22

[ 2010 Pittsburgh: Moved to NAD EditorialResolved. Rationale added below. ]

Date: 2009-11-18.00:00:00

The current description of the associated state in [futures.state] does not allow for futures created by an async call. The description therefore needs to be extended to cover that.

History
Date User Action Args
2010-12-05 00:09:22adminsetstatus: nad editorial -> resolved
2010-10-21 18:28:33adminsetmessages: + msg1380
2010-10-21 18:28:33adminsetmessages: + msg1379
2010-10-21 18:28:33adminsetmessages: + msg1378
2009-11-18 00:00:00admincreate