-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Do not normalize field types in elaborate_drops. #106905
Conversation
r? @Nilstrieb (rustbot has picked a reviewer for you, use r? to override) |
1b5aec2
to
89fb42a
Compare
let field_ty = | ||
tcx.normalize_erasing_regions(self.elaborator.param_env(), f.ty(tcx, substs)); |
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.
Do you know why the normalize was here in the first place?
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.
I don't know. The call to normalize dates back to 2016.
This makes sense to me, but I'm not that familiar with all of this code so I'll hand it over for a final review. |
@bors r+ |
⌛ Testing commit 89fb42a with merge c97b37ddbe5273f50fe36a52a72bc5af1e8dec2a... |
💔 Test failed - checks-actions |
🤔
|
Will re-assign to author to investigate the tests new breakage. Feel free to request a review with @rustbot author |
The job Click to see the possible cause of the failure (guessed by this bot)
|
@bors r- (was inadvertently re-queued by a homu sync) |
☔ The latest upstream changes (presumably #111680) made this pull request unmergeable. Please resolve the merge conflicts. |
Fixes #106444