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.
shared_future
should support an efficient move constructorSection: 33.10.8 [futures.shared.future] Status: Resolved Submitter: LWG Opened: 2009-06-28 Last modified: 2021-06-06
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: