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.
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
Handle bindings in substructure of patterns with type ascriptions #55274
Handle bindings in substructure of patterns with type ascriptions #55274
Changes from all commits
26c4069
54681b0
36d8432
28ce99d
b569caf
740e8a3
7e76196
f09a0eb
92cbe47
47e2d82
82ab668
639a3ff
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
Is there any particular reason for this? I guess just because nobody has any reason to.
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.
Well, the existing MIR visit methods take a
PlaceElem
, not aProjectionElem<(), ()>
. So it would have been a bit of extra complexity in the visit API to try to support it ... and to what end? There isn't any recursive structure to visit, and you would probably want to know all about the surrounding context when inspecting any particularProjectionElem<(), ()>
within theUserTypeProjection
... so better to just do it explicitly in one'svisit_user_type_projection
method?