Fix unreachable code warning in range formatter - #4932
Open
Zhao0335 wants to merge 1 commit into
Open
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The range formatter constructor returned from a compile-time branch for every
non-set range, leaving the bracket customization after the return. New MSVC
versions diagnose that statement as unreachable when sequence range formatters
are instantiated.
Invert the condition and only customize brackets for set ranges. This preserves
the behavior for both pre-C++20 and C++20 builds while allowing
if constexprto discard the unused branch.
Testing:
/W4: theranges.hC4702 warning reproduced before the changeand is absent after it
ranges-testpassedchrono-test.localeandunicode-test.legacy_localefail under this machine's zh-CN locale