Implement LWG-4312 Const and value category mismatch for allocator_arg_t/allocator_arg in the description of uses-allocator construction
#5904
+106
−5
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
StephanTLavavej
approved these changes
Nov 24, 2025
Member
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
Member
😸 😺 🐈 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Fixes #5866.
Note that the difference between
allocator_arg/allocator_arg_t{}is only observable for (contrived) user-defined types, so we only need to modify_Tuple_valand_Uses_alloc_construct_non_pair(pre-C++20 only).For
scoped_allocator_adaptorandpolymorphic_allocator, the changes make the pre-C++20 behavior more consistent and closer to C++20 behavior.