-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Documenting binding syntax for pattern matching #10917
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from 1 commit
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -476,7 +476,7 @@ can be expressed with two dots, as in `M..N`. The underscore (`_`) is | |
a wildcard pattern that matches any single value. (`..`) is a different | ||
wildcard that can match one or more fields in an `enum` variant. | ||
|
||
The patterns in a match arm are followed by a fat arrow, `=>`, then an | ||
The patterns in a `match` arm are followed by a fat arrow, `=>`, then an | ||
expression to evaluate. Each case is separated by commas. It's often | ||
convenient to use a block expression for each case, in which case the | ||
commas are optional. | ||
|
@@ -542,6 +542,29 @@ Let bindings only work with _irrefutable_ patterns: that is, patterns | |
that can never fail to match. This excludes `let` from matching | ||
literals and most `enum` variants. | ||
|
||
The pattern of a `match` arm can also be bound to a variable for use in the | ||
`match` arm's expression. | ||
|
||
~~~~ | ||
match (1, 2) { | ||
c@(a, b) => println!("{:?} {:?} {:?}", a, b, c) | ||
} | ||
~~~~ | ||
|
||
This will print `1 2 (1, 2)`. `c` is bound to the pattern `(a, b)`, and as | ||
`a` and `b` are respectively bound to `1` and `2`, `c` comes out to `(1, 2)`. | ||
The bound variable `c` is only usable in the expression following the arrow `=>`. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. "The bound variable |
||
|
||
Pattern binding can also be used in conjuntion with guard clauses. | ||
|
||
~~~~ | ||
match (1, 2) { | ||
c@(a, b) if a > 0 => println!("First arm {:?}", c), | ||
c@(_, b) if b < 2 => println!("Second arm {:?}", c), | ||
_ => {} | ||
} | ||
~~~~ | ||
|
||
## Loops | ||
|
||
`while` denotes a loop that iterates as long as its given condition | ||
|
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could you write this as
c @ (a, b)
(just stylistic; and do it below too). Also, writing thea
andb
prints as{}
rather than{:?}
would be nicer.