This page is a snapshot from the LWG issues list, see the Library Active Issues List for more information and the meaning of NAD Editorial status.

1512. Conflict in specification: block or join?

Section: 30.6.9 [futures.async] Status: NAD Editorial Submitter: INCITS Opened: 2010-08-25 Last modified: 2016-02-10

Priority: Not Prioritized

View all other issues in [futures.async].

View all issues with NAD Editorial status.


Addresses US-205

30.6.9 [futures.async] p. 3: The third sentence says "If the invocation is not deferred, a call to a waiting function on an asynchronous return object that shares the associated asynchronous state created by this async call shall block until the associated thread has completed." The next sentence says "If the invocation is not deferred, the join() on the created thread..." Blocking until a thread completes is not necessarily a join.

[ Resolution proposed by ballot comment: ]

Decide whether the requirement is to block until finished or to call join, and rewrite to match.

Proposed resolution: