Main template
void set_value_at_thread_exit( const R& value );
(1) (since C++11)void set_value_at_thread_exit( R&& value );
(2) (since C++11)void set_value_at_thread_exit( R& value );
(3) (since C++11)void set_value_at_thread_exit();
(4) (since C++11)Stores the value into the shared state without making the state ready immediately. The state is made ready when the current thread exits, after all variables with thread-local storage duration have been destroyed.
The operation behaves as though set_value, set_exception, set_value_at_thread_exit, and set_exception_at_thread_exit acquire a single mutex associated with the promise object while updating the promise object.
Calls to this function do not introduce data races with calls to get_future (therefore they need not synchronize with each other).
[edit] Parameters value - value to store in the shared state [edit] Return value(none)
[edit] Exceptionsstd::future_error on the following conditions:
Additionally:
1) Any exception thrown by the constructor selected to copy an object of type R.
2) Any exception thrown by the constructor selected to move an object of type R.
Output:
Waiting... Done! Result is: 9[edit] Defect reports
The following behavior-changing defect reports were applied retroactively to previously published C++ standards.
DR Applied to Behavior as published Correct behavior LWG 2098 C++11 it was unclear which exceptions are required to be thrown made clear [edit] See alsoRetroSearch 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