We've already implemented these LWG issue resolutions that were just accepted at the Nov 2024 meeting:
- LWG-3210
allocate_shared is inconsistent about removing const from the pointer passed to allocator construct and destroy
- Implemented since 2019 (internal MSVC-PR-183222). Resolved when LWG-3216 "Rebinding the allocator before calling
construct/destroy in allocate_shared" was accepted.
- LWG-4024 Underspecified destruction of objects created in
std::make_shared_for_overwrite/std::allocate_shared_for_overwrite
- LWG-4154 The Mandates for
std::packaged_task's constructor from a callable entity should consider decaying
Now we need to remove our comments about speculatively implementing these issues.
We've already implemented these LWG issue resolutions that were just accepted at the Nov 2024 meeting:
allocate_sharedis inconsistent about removingconstfrom the pointer passed to allocatorconstructanddestroyconstruct/destroyinallocate_shared" was accepted.std::make_shared_for_overwrite/std::allocate_shared_for_overwrite<memory>: Add different control block types forallocate_shared_for_overwrite#4274std::packaged_task's constructor from a callable entity should consider decaying<future>: Makepackaged_taskaccept move-only functors #4946Now we need to remove our comments about speculatively implementing these issues.