1162. shared_future should support an efficient move constructor

Section: 33.6.8 [futures.shared_future] Status: Resolved Submitter: LWG Opened: 2009-06-28 Last modified: 2016-02-10

Priority: Not Prioritized

View all other issues in [futures.shared_future].

View all issues with Resolved status.

Discussion:

Addresses UK 337

Description

shared_future should support an efficient move constructor that can avoid unnecessary manipulation of a reference count, much like shared_ptr

Suggestion

Add a move constructor

Notes

Create an issue. Detlef will look into it.

[ 2009-07 Frankfurt ]

Pending a paper from Anthony Williams / Detlef Vollmann.

[ 2009-10-14 Pending paper: N2967. ]

[ 2009-10 Santa Cruz: ]

NAD EditorialResolved. Addressed by N2997.

Proposed resolution: