Record pattern matching. #755
Merged
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.
This PR adds support for records in pattern matching and an update to pattern matching itself.
Fields can be matched with the same syntax as records:
The other change is that patterns are now limited to the following ones:
Maybe(...)
{...}
{a, b}
[...]
a
"a"
0.1
true
It's needed, so exhaustiveness checking works reliably, for example:
In the example above, we can't be sure which branch is redundant, since we don't know the value of
otherValue
at compile time.I'll try to do explore how to enable this in the future. Elixir has it, but they don't support exhaustiveness, Gleam, Rust and Elm don't allow this, not sure if other languages do. If anyone has research on it, let me know :)