Similar to native match pattern for tuple structs, make matches_pattern enforce exhaustive field checks for tuple structs by default, to be suppressed by explicit .. at the end of the pattern.
#538
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
copybara-service
bot
force-pushed
the
test_704273542
branch
3 times, most recently
from
dfb10c1 to
dbfddfb
Compare
…ern` enforce exhaustive field checks for tuple structs by default, to be suppressed by explicit `..` at the end of the pattern. This change is not backward-compatible since it enforces field exhaustiveness by default in the absence of a trailing `..` in the pattern. Fixes #447 PiperOrigin-RevId: 705914628
copybara-service
bot
force-pushed
the
test_704273542
branch
from
dbfddfb to
a17b655
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Similar to native match pattern for tuple structs, make
matches_patternenforce exhaustive field checks for tuple structs by default, to be suppressed by explicit..at the end of the pattern.This change is not backward-compatible since it enforces field exhaustiveness by default in the absence of a trailing
..in the pattern.Fixes #447