-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Subpart8 for async drop (major2) - dropline in scopes for potentially async drops #129744
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
Subpart8 for async drop (major2) - dropline in scopes for potentially async drops #129744
Conversation
Some changes occurred in compiler/rustc_codegen_cranelift cc @bjorn3 Some changes occurred to the CTFE / Miri engine cc @rust-lang/miri Some changes occurred to MIR optimizations cc @rust-lang/wg-mir-opt This PR changes Stable MIR cc @oli-obk, @celinval, @ouz-a This PR changes MIR cc @oli-obk, @RalfJung, @JakobDegen, @davidtwco, @celinval, @vakaras |
@azhogin please read what I wrote in one of your other PRs. You're spamming tons of people here.
|
0e47a7e
to
b755978
Compare
31bf8a4
to
2e77402
Compare
☔ The latest upstream changes (presumably #130165) made this pull request unmergeable. Please resolve the merge conflicts. |
r? @nikomatsakis is going to look into this |
f0997e3
to
4f14fe1
Compare
…p from previous async drop glue implementation
4f14fe1
to
59b9945
Compare
The job Click to see the possible cause of the failure (guessed by this bot)
|
☔ The latest upstream changes (presumably #139578) made this pull request unmergeable. Please resolve the merge conflicts. |
This is subpart 8 PR of #123948, just for review purposes.
Scopes processing for generate async drop preparations.
In scopes processing we need to consider potentially async drops as a hidden Yield and prepare dropline in the similar way as for Yield terminator.
Review only last commit, based on previous PR #129742