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.
Section: 30.6 [futures] Status: Resolved Submitter: INCITS Opened: 2010-08-25 Last modified: 2016-02-10
Priority: Not Prioritized
View all other issues in [futures].
View all issues with Resolved status.
The specification for managing associated asynchronous state is confusing, sometimes omitted, and redundantly specified.
[ Resolution proposed by ballot comment: ]
Define terms-of-art for releasing, making ready, and abandoning an associated asynchronous state. Use those terms where appropriate. See Appendix 1 - Additional Details
Resolved in Batavia by accepting n3192.