Created on 2010-08-25.00:00:00 last changed 171 months ago
Proposed resolution:
3 The effect of calling any member function other than the destructor, the copy-assignment operator, the move-assignment operator, or valid() on a shared_future object for which valid() == false is undefined.
? The effect of calling any member function other than the destructor, the copy-assignment operator, or valid() on a atomic_future object for which valid() == false is undefined.
[ 2010-11-02 Daniel translates proposed changes into specific deltas and comments: ]
While applying the wording, I notice that [futures.shared_future]/3 does speak of the move-assignment operator, and not of the copy-assignment operator. atomic_future obviously needs this to be true for the copy-assignment operator, but I strongly assume that shared_future needs to mention both special member assignment operators in this paragraph. To keep this consistent, the following P/R also provides wording to fix the corresponding location for shared_future.
[ Resolution proposed by ballot comment: ]
Add a new paragraph after [futures.atomic_future]/2 with the same words as [futures.shared_future]/3.
Addresses US-203
Both future and shared_future specify that calling most member functions on an object for which valid() == false produces undefined behavior. There is no such statement for atomic_future.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-11-11 19:19:17 | admin | set | status: open -> nad editorial |
| 2010-11-02 20:27:27 | admin | set | messages: + msg5273 |
| 2010-11-02 20:27:27 | admin | set | messages: + msg5272 |
| 2010-11-02 20:27:27 | admin | set | messages: + msg5271 |
| 2010-10-24 03:04:13 | admin | set | messages: + msg4969 |
| 2010-08-25 00:00:00 | admin | create | |