Created on 2010-01-26.00:00:00 last changed 170 months ago
Rationale:
Solved by N3073.
[ 2010 Pittsburgh: Moved to NAD Editorial. Rationale added below. ]
The current requirements for a conforming implementation of std::exception_ptr ([propagation]/1-6) does not clarify whether the expression
e1 != e2 e1 != nullptr
with e1 and e2 being two values of type std::exception_ptr are supported or not. Reason for this oddity is that the concept EqualityComparable does not provide operator !=.
For the same reason programmers working against the types X::pointer, X::const_pointer, X::void_pointer, and X::const_void_pointer of any allocator concept X ([allocator.requirements]/4 + Table 40) in a generic context can not rely on the availability of the != operation, which is rather unnatural and error-prone.
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2010-11-19 19:04:45 | admin | set | status: nad editorial -> resolved |
| 2010-10-21 18:28:33 | admin | set | messages: + msg1538 |
| 2010-10-21 18:28:33 | admin | set | messages: + msg1537 |
| 2010-01-26 00:00:00 | admin | create | |