mir_build: Don't use a mixture of THIR pattern kinds for pin-patterns #150121
+35
−40
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.
While looking for improvements to match-lowering, I had been trying to figure out why pin-patterns sometimes use
PatKind::Derefand sometimes usePatKind::DerefPattern, which seemed confusing to me. In particular, both pattern kinds are being used with an inner type of&or&mut, which is very surprising.The conclusion I came to was that
DerefPattern(normally associated with calls to Deref/DerefMut) was only being used for implicit pin-patterns produced by match-ergonomics adjustment, whereasDerefwas being used for explicit pin-patterns.The inconsistency seems like a mistake to me, so this PR removes all uses of
DerefPatternfor pin-patterns, and consistently usesPatKind::Dereffor pin-patterns instead. I'm not entirely happy with that outcome, because I think pin-patterns should probably have their ownthir::PatKindvariant, but this change will at least make that easier to achieve in a later PR.r? Nadrieril