Created on 2010-08-25.00:00:00 last changed 170 months ago
Proposed resolution:
See n3140.
[ 2010-11 Batavia: ]
Resolved by adopting n3140.
[ 2010-10-24 Daniel adds: ]
Accepting n3140 would solve this issue.
[ Resolution proposed by ballot comment ]
Replace the usage of std::move by that of std::forward and replace MoveConstructible and CopyConstructible requirements by other requirements.
Addresses DE-16
Several pair and tuple functions in regard to move operations are incorrectly specified if the member types are references, because the result of a std::move cannot be assigned to lvalue-references. In this context the usage of the requirement sets MoveConstructible and CopyConstructible also doesn't make sense, because non-const lvalue-references cannot satisfy these requirements.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-11-18 14:01:09 | admin | set | messages: + msg5392 |
| 2010-11-18 14:01:09 | admin | set | status: nad editorial -> resolved |
| 2010-11-11 03:10:11 | admin | set | status: open -> nad editorial |
| 2010-10-25 21:30:05 | admin | set | messages: + msg5135 |
| 2010-10-25 01:00:51 | admin | set | messages: + msg5114 |
| 2010-10-24 22:33:31 | admin | set | messages: + msg5080 |
| 2010-10-24 10:50:39 | admin | set | messages: + msg4999 |
| 2010-08-25 00:00:00 | admin | create | |