Created on 2023-03-05.00:00:00 last changed 4 months ago
[ St. Louis 2024-06-24 Status changed: Tentatively NAD → NAD. ]
[ 2023-03-22; Reflector poll ]
Set status to Tentatively NAD.
Not all uses-allocator construction is done using construct_at
.
std::tuple<const T>(allocator_arg, alloc)
does
uses-allocator construction of a const type, so we can't make it ill-formed.
LWG 3870 made std::construct_at unable to create an object of a cv-qualified type, which affects std::uninitialized_construct_using_allocator. However, uses-allocator construction is currently not required to be equivalent to some call to std::uninitialized_construct_using_allocator, which possibly implies that uses-allocator construction of a cv-qualified type may still be required to be well-formed.
Should we make such construction ill-formed?History | |||
---|---|---|---|
Date | User | Action | Args |
2024-06-24 16:21:35 | admin | set | messages: + msg14200 |
2023-03-22 22:35:08 | admin | set | messages: + msg13471 |
2023-03-22 22:35:08 | admin | set | status: new -> nad |
2023-03-05 00:00:00 | admin | create |