<string>: Fix handling for char_traits<unicorn>
#4951
Merged
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
AlexGuteniev
approved these changes
Sep 12, 2024
tests/std/tests/GH_004930_char_traits_user_specialization/test.cpp
Outdated
Show resolved
Hide resolved
tests/std/tests/GH_004930_char_traits_user_specialization/test.cpp
Outdated
Show resolved
Hide resolved
tests/std/tests/GH_004930_char_traits_user_specialization/test.cpp
Outdated
Show resolved
Hide resolved
StephanTLavavej
approved these changes
Sep 19, 2024
|
I'm mirroring this to the MSVC-internal repo - please notify me if any further changes are pushed. |
🧵 🦄 🛠️ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 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 #4930. Ideally, when
Tis an implementation-controlled type, special handling should be enabled forchar_traits<T>to reject more unintended element types. But the complete work is impractical, so this PR restricts the handling to arithmetic types andnullptr_t.Drive-by changes:
static_assertmessage to mentionchar8_t.TRANSITIONcomments in<regex>, but test coverage is currently missing (which would be complicated and weird).