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
Diagnose anonymous lifetimes errors more uniformly between async and regular fns #97023
Diagnose anonymous lifetimes errors more uniformly between async and regular fns #97023
Changes from all commits
8da2707
da175c7
7b86c6f
3162b33
0cf79d7
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.
This code is a bit sus to me. This relies on us not having duplicate
BoundRegionKind
s in binders. This is how the compiler behaves today (or should barring bugs), but there isn't nothing to say that we can't (you could, for example, imagine that we drop the anon index).This makes more sense as just a
Vec
where each index is just theBoundRegionKind
that corresponds to the binder (or just some placeholder value for non-regions) and then useBoundRegion.var.as_usize()
as an index into that vec, which is exactly how bound variables work.(I'm making these changes currently for the bug below).
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.
This broke cases under
-Zverbose
where we try to print a named bound region. Above, we don't insert them in theregion_map
but here we try to lookup the variable anyways.