New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
P2875 R4 Undeprecate polymorphic_allocator::destroy
For C++26
#1530
Comments
Was discussed on LEWG Mailing List closed on 2023-07-25 (https://lists.isocpp.org/lib-ext/2023/07/25577.php) No consensus for forwarding, there was a request for additional motivation in the paper, Author will come back with a new revision. |
P2875R1 Undeprecate |
polymorphic_allocator::destroy
For C++26polymorphic_allocator::destroy
For C++26
P2875R2 Undeprecate |
polymorphic_allocator::destroy
For C++26polymorphic_allocator::destroy
For C++26
2024-01-23 Library Evolution TeleconP2875R1: Undeprecate polymorphic_allocator::destroy For C++26 2024-01-23 Library Evolution Telecon Minutes Champion: Alisdair Meredith Chair: Ben Craig Minute Taker: Eddie Nolan SummaryPOLL: Modify P2875R1 (Undeprecate polymorphic_allocator::destroy For C++26) by adding removal migration examples, and then send the revised paper to LWG for C++26 classified as B3, to be confirmed with a Library Evolution electronic poll.
Attendance: 22 # of Authors: 1 Author's Position: SF Outcome: Consensus in favor Comments: SA: LEWG has a bad history of reconsidering decisions made in good faith, and this is a bad idea. Haven't seen clear evidence that this was a mistake. Next StepsAdd an example of what a user would need to do to replace a call to polymorphic_allocator::destroy. |
Note: We will have R3 voted in the electronic poll, as the author already published an R2. |
P2875R3 Undeprecate |
polymorphic_allocator::destroy
For C++26polymorphic_allocator::destroy
For C++26
P2875R4 Undeprecate |
polymorphic_allocator::destroy
For C++26polymorphic_allocator::destroy
For C++26
P2875R0 Undeprecate
polymorphic_allocator::destroy
For C++26 (Alisdair Meredith)The text was updated successfully, but these errors were encountered: