This page is a snapshot from the LWG issues list, see theLibrary Active Issues List for more information and the meaning ofResolved status.
Section: 32.10[futures]Status:ResolvedSubmitter: Jonathan WakelyOpened: 2009-11-22Last modified: 2016-01-28
Priority:Not Prioritized
View all otherissues in [futures].
View all issues withResolved status.
Discussion:
[futures.unique_future]/1 should be updated to mentionasync.
[futures.shared_future]/1 should also be updated forasync. That paragraph also says
... Its value or exception can be set by use of a
shared_future,promise(32.10.6[futures.promise]), orpackaged_task(32.10.10[futures.task]) object that shares the same associated state.
How can the value be set by ashared_future?
99 [futures.atomic_future]/1 says
An
atomic_futureobject can only be created by use of apromise(32.10.6[futures.promise]) orpackaged_task(32.10.10[futures.task]) object.
which is wrong, it's created from astd::future, which couldhave been default-constructed. That paragraph should be closer to thetext of [futures.shared_future]/1, and should also mentionasync.
[2010 Pittsburgh: Moved toNAD EditorialResolved. Rationale added below.]
Rationale:
Solved byN3058.
Proposed resolution: