Title
constructor shared_future(unique_future) by value?
Status
nad editorial
Section
[futures.shared.future]
Submitter
Thomas J. Gritzan

Created on 2009-04-03.00:00:00 last changed 171 months ago

Messages

Date: 2010-10-21.18:28:33

Proposed resolution:

Change the synopsis in [futures.shared_future]:

shared_future(unique_future<R>&& rhs);

Change the definition of the constructor in [futures.shared_future]:

shared_future(const unique_future<R>&& rhs);
Date: 2009-07-05.00:00:00

[ 2009-07-05 Daniel notes: ]

The proposed change has already been incorported into the current working draft N2914.

Date: 2010-10-21.18:28:33

[ Batavia (2009-05): ]

We agree with the proposed resolution.

Move to Tentatively Ready.

Date: 2009-04-03.00:00:00

In the shared_future class definition in [futures.shared_future] the move constructor that constructs a shared_future from an unique_future receives the parameter by value. In paragraph 3, the same constructor receives it as const value.

I think that is a mistake and the constructor should take a r-value reference:

shared_future(unique_future<R>&& rhs);
History
Date User Action Args
2010-10-21 18:28:33adminsetmessages: + msg755
2010-10-21 18:28:33adminsetmessages: + msg754
2010-10-21 18:28:33adminsetmessages: + msg753
2009-04-03 00:00:00admincreate