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.

1049. Move assignment of promise inverted

Section: 32.9.6 [futures.promise] Status: Resolved Submitter: Alisdair Meredith Opened: 2009-03-12 Last modified: 2016-02-10

Priority: Not Prioritized

View other active issues in [futures.promise].

View all other issues in [futures.promise].

View all issues with Resolved status.


Addresses UK 339 [CD1]

Move assignment is going in the wrong direction, assigning from *this to the passed rvalue, and then returning a reference to an unusable *this.

[ Summit: ]

Agree, move to Review.

[ Batavia (2009-05): ]

We recommend deferring this issue until after Detlef's paper (on futures) has been issued.

[ 2009-10 Santa Cruz: ]

NAD EditorialResolved. Addressed by N2997.

Proposed resolution:

Strike 32.9.6 [futures.promise] p6 and change p7:

promise& operator=(promise&& rhs);

-6- Effects: move assigns its associated state to rhs.

-7- Postcondition: *this has no associated state. associated state of *this is the same as the associated state of rhs before the call. rhs has no associated state.