This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of C++17 status.
Section: 30.6.7 [futures.unique_future] Status: C++17 Submitter: Agustín K-ballo Bergé Opened: 2015-09-03 Last modified: 2017-08-01
View all other issues in [futures.unique_future].
View all issues with C++17 status.
The standard is usually very explicit on when a shared state is released, except for future::get for which it only states valid() == false as a postcondition.
[2016-08 - Chicago]
Thurs AM: Moved to Tentatively Ready
This wording is relative to N4527.
Modify 30.6.7 [futures.unique_future] as indicated:
R future::get(); R& future<R&>::get(); void future<void>::get();
-14- Note: as described above, the template and its two required specializations differ only in the return type and return value of the member function get.-15- Effects:
wait()s until the shared state is ready, then retrieves the value stored in the shared state