Title
future::valid should be callable on an invalid future
Status
resolved
Section
[futures.unique.future]
Submitter
Jonathan Wakely

Created on 2009-11-22.00:00:00 last changed 170 months ago

Messages

Date: 2010-10-21.18:28:33

Proposed resolution:

Change [futures.unique_future]/3:

The effect of calling any member function other than the destructor, or the move-assignment operator, or valid, on a future object for which valid() == false is undefined.

Date: 2010-10-21.18:28:33

Rationale:

Solved by N3058.

Date: 2010-12-05.00:09:22

[ 2010 Pittsburgh: ]

Moved to NAD EditorialResolved. Rationale added below.

Date: 2009-12-08.00:00:00

[ 2009-12-08 Moved to Tentatively Ready after 5 positive votes on c++std-lib. ]

Date: 2009-11-22.00:00:00

[futures.unique_future]/3 says:

The effect of calling any member function other than the destructor or the move-assignment operator on a future object for which valid() == false is undefined.

This means calling future::valid() is undefined unless it will return true, so you can only use it if you know the answer!

History
Date User Action Args
2010-12-05 00:09:22adminsetstatus: nad editorial -> resolved
2010-10-21 18:28:33adminsetmessages: + msg1398
2010-10-21 18:28:33adminsetmessages: + msg1397
2010-10-21 18:28:33adminsetmessages: + msg1396
2010-10-21 18:28:33adminsetmessages: + msg1395
2009-11-22 00:00:00admincreate