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.

1503. "associated asynchronous state" must go

Section: 30.6.5 [futures.state] Status: NAD Editorial Submitter: Switzerland Opened: 2010-08-25 Last modified: 2016-02-10

Priority: Not Prioritized

View all other issues in [futures.state].

View all issues with NAD Editorial status.


Addresses CH-35

The term "associated asynchronous state" is long, ugly and misleading terminology. When introduced we agreed upon that we should come up with a better name. Here it is: "liaison state". Since the state is hidden and provides synchronization of a future with its corresponding promise, we believe "liaison state" is a much better and shorter name (liaison ~ (typically hidden) relationship)

[ Resolution proposed by ballot comment: ]

Change all occurrences of "associated asynchronous state" to "liaison state".

Proposed resolution:

The project editor may supply a more appopriate term, or use "liaison state", at his own discretion.