checks/errors: Fix non-exhaustive pattern matching for literals #4364
+189
−22
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.
The compiler previously treated literal patterns (like 0, 'a', or true) as
wildcards, causing the exhaustiveness checker to incorrectly accept incomplete
match blocks.
This patch modifies lower_pattern to lower literals into integer ranges
using std::strtoll (for -fno-exceptions compatibility). It updates
split_constructors to handle finite boolean universes and defaults other
scalars to wildcards.
Additionally, WitnessMatrix::apply_constructor and WitnessPat::to_string
are updated to handle INT_RANGE constructors, preventing Internal Compiler
Errors (ICEs). Existing tests were updated to include wildcard arms to
satisfy the correct exhaustiveness checks.
Fixes #4296
gcc/rust/ChangeLog:
gcc/testsuite/ChangeLog:
make check-rustpasses locallyclang-formatgcc/testsuite/rust/