-
Notifications
You must be signed in to change notification settings - Fork 1.6k
Don't lint while_let_loop
when significant drop order would change
#8666
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
r? @camsteffen (rust-highfive has picked a reviewer for you, use r? to override) |
91e4214
to
b627856
Compare
while_let_loop
when significant drop order would change
b627856
to
b5bffbb
Compare
☔ The latest upstream changes (presumably #8647) made this pull request unmergeable. Please resolve the merge conflicts. |
r? @dswij |
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 looks great, thanks for the changes!
Looks like there's some conflicts, and after that I think this is good to merge |
b5bffbb
to
e48c92a
Compare
e48c92a
to
adbc849
Compare
Thanks! @bors r+ |
📌 Commit adbc849 has been approved by |
☀️ Test successful - checks-action_dev_test, checks-action_remark_test, checks-action_test |
fixes #7226
fixes #7913
fixes #5717
For #5717 it may not stay fully fixed. This is only completely fixed right now due to all the allowed drop impls have
#[may_dangle]
on their drop impls. This may get changed in the future based on how significant drops are determined, but the example listed withRefCell
shouldn't break.changelog: Don't lint
while_let_loop
when the order of significant drops would change