Open jwakely opened 1 year ago
The issue was discussed in Library Evolution Telecon on 2023-07-25 Full Minutes.
No polls were taken
Jonathan will come back with a proposed resolution that aligns with Tim’s suggestion, LEWG will vote on the proposed resolution.
Please see the updated proposed resolution for LWG3003, which would resolve both 3003 and 2095.
The new approach is:
promise
.uses_allocator
specialization for promise
.packaged_task
.uses_allocator
specialization for packaged_task
.packaged_task::reset()
to deal with allocators.
https://cplusplus.github.io/LWG/issue2095 https://cplusplus.github.io/LWG/issue3003
These two issues suggest two contradictory changes to
std::promise
. LWG would like LEWG to decide whether to add the missing constructors, or remove the existing allocator-extended constructors.