mirror of
https://github.com/google/comprehensive-rust.git
synced 2025-05-16 23:55:42 +02:00
Briefly touch on match ergonomics (#2581)
This is done in the speaker notes as it's a relatively minor point, but one that students should have in the back of their mind when they wonder, "hey, how does a `&Foo` match against `Foo` patterns??"
This commit is contained in:
parent
5b03ea6ca5
commit
f19bb8f10d
@ -14,6 +14,12 @@ Like tuples, Struct can also be destructured by matching:
|
|||||||
|
|
||||||
- Change the literal values in `foo` to match with the other patterns.
|
- Change the literal values in `foo` to match with the other patterns.
|
||||||
- Add a new field to `Foo` and make changes to the pattern as needed.
|
- Add a new field to `Foo` and make changes to the pattern as needed.
|
||||||
|
- Try `match &foo` and check the type of captures. The pattern syntax remains
|
||||||
|
the same, but the captures become shared references. This is
|
||||||
|
[match ergonomics](https://rust-lang.github.io/rfcs/2005-match-ergonomics.html)
|
||||||
|
and is often useful with `match self` when implementing methods on an enum.
|
||||||
|
- The same effect occurs with `match &mut foo`: the captures become exclusive
|
||||||
|
references.
|
||||||
- The distinction between a capture and a constant expression can be hard to
|
- The distinction between a capture and a constant expression can be hard to
|
||||||
spot. Try changing the `2` in the second arm to a variable, and see that it
|
spot. Try changing the `2` in the second arm to a variable, and see that it
|
||||||
subtly doesn't work. Change it to a `const` and see it working again.
|
subtly doesn't work. Change it to a `const` and see it working again.
|
||||||
|
Loading…
x
Reference in New Issue
Block a user