As a newcomer to Rust, I\'ve stumbled upon two apparently valid ways of running a match
on a reference type.
I\'ve defined an enum:
enum
You can't move out of an immutable reference, so you don't have to worry about that being the case.
It's worth considering that one would expect matches to work somewhat akin to (Partial
)Eq
, and that takes &self
. In other words, one would expect it to take a reference implicitly unless forced. This is easily confirmed with a little experimentation.
It's worth noting that *self
is not a move - it's a reference to a memory location. It is thus an lvalue. Ergo,
When the head expression is an lvalue, the match does not allocate a temporary location (however, a by-value binding may copy or move from the lvalue).
https://doc.rust-lang.org/reference.html#match-expressions
If a temporary location is not allocated, a move cannot occur. Thus the behaviour is guaranteed. As the parenthetical notes, internal data can still get moved out from destructuring pattern, which would cause a problem. This, however, is true regardless of whether you are matching on self
or *self
.
Using *self
seems to be an informal idiom, and should be preferred.