-
Notifications
You must be signed in to change notification settings - Fork 13.6k
Fix de-deduplication for closure debuginfo #27346
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
Conversation
Closure variables represent the closure environment, not the closure function, so the identifier used to ensure that the debuginfo is unique for each kind of closure needs to be based on the closure upvars and not the function signature.
r? @arielb1 (rust_highfive has picked a reviewer for you, use r? to override) |
Thanks for the PR! I'll take a look at this as soon as I find the time. —Reply to this email directly or view it on GitHub. |
@bors: r+ |
📌 Commit 218eccf has been approved by |
Thanks, this is certainly more correct than what we do now, especially after closure type descriptions have been fixed. |
Closure variables represent the closure environment, not the closure function, so the identifier used to ensure that the debuginfo is unique for each kind of closure needs to be based on the closure upvars and not the function signature.
👌🐤👍 |
Closure variables represent the closure environment, not the closure
function, so the identifier used to ensure that the debuginfo is unique
for each kind of closure needs to be based on the closure upvars and not
the function signature.