Implement LWG-3677 for tuple#5669
Merged
Merged
Conversation
StephanTLavavej
approved these changes
Oct 9, 2025
Member
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
Member
|
Every PR brings us one step closer to the vision: an LWG issue resolution in every home and on every desk. 💻 🖥️ 😹 |
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
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.
Related to #3220.
LWG-3677 changed the dispatch mechanism for uses-allocator construction, which should also affect
tuple'sallocator_arg_tconstructors per [tuple.cnstr]/33.Unlike the special handling for
pair(see #5668), this change won't complicatetuplea lot, And it seems consistent to me to apply the change totuple.