Created on 2010-06-21.00:00:00 last changed 162 months ago
Proposed resolution:
Change the first bullet item in [futures.task.members] p. 17:
void operator()(ArgTypes... args);15 ...
16 ...
17 Error conditions:
- promise_already_satisfied if the
associated asynchronous state is already readystored task has already been invoked.- no_state if *this has no associated asynchronous state.
Change the first bullet item in [futures.task.members] p. 21:
void make_ready_at_thread_exit(ArgTypes... args);19 ...
20 ...
21 Error conditions:
- promise_already_satisfied if the
associated asynchronous state already has a stored value or exceptionstored task has already been invoked.- no_state if *this has no associated asynchronous state.
[ Adopted at Madrid, 2011-03 ]
[ 2011-02-17 Anthony provides an alternative resolution ]
Previous proposed resolution:
Change the first bullet item in [futures.task.members] /22:
void operator()(ArgTypes... args);20 ...
21 ...
22 Error conditions:
- promise_already_satisfied if
the associated asynchronous state is already readyoperator() has already been called.- no_state if *this has no associated asynchronous state.
The Throws clause for packaged_task::operator() says that it throws "a future_error exception object if there is no associated asynchronous state or the stored task has already been invoked." However, the Error Conditions clause does not define an error condition when the stored task has already been invoked, only when the associated state is already ready (i.e. the invocation has completed).
History | |||
---|---|---|---|
Date | User | Action | Args |
2011-08-23 20:07:26 | admin | set | status: wp -> c++11 |
2011-04-11 11:23:23 | admin | set | status: immediate -> wp |
2011-03-24 21:43:06 | admin | set | messages: + msg5707 |
2011-03-24 21:43:06 | admin | set | status: new -> immediate |
2011-02-17 18:45:24 | admin | set | messages: + msg5501 |
2010-11-07 17:36:56 | admin | set | messages: + msg5299 |
2010-06-21 00:00:00 | admin | create |