-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
Subpart11 for async drop (major5) - shims codegen #129747
base: master
Are you sure you want to change the base?
Subpart11 for async drop (major5) - shims codegen #129747
Conversation
@azhogin I don't think you've made your code easier to review at all. |
/// Allows implementing `AsyncDrop`. | ||
(incomplete, async_drop, "CURRENT_RUSTC_VERSION", Some(126482)), |
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.
Unstable library items do not get compiler feature gates.
/// Allows implementing `AsyncDrop`. | |
(incomplete, async_drop, "CURRENT_RUSTC_VERSION", Some(126482)), |
4d2435f
to
33841e6
Compare
…p from previous async drop glue implementation
33841e6
to
327f30e
Compare
327f30e
to
1e84499
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 |
This is subpart 11 PR of #123948, just for review purposes.
Shims for:
async_drop_in_place<T>(dropee) -> async_drop_in_place<T>(dropee)::{{closure0}}
async_drop_in_place<T>(dropee)::{{closure0}}
for non-coroutine dropee types. When we need to generate drop glue (ladder) using drop elaboration and then StateTransform it into coroutine poll function.async_drop_in_place<T>(dropee)::{{closure0}}
for coroutine dropee types. When we need to proxy call already generatedcoroutine_drop_async
(produced in StateTransform pass of the coroutine T).Review only last commit, based on previous PR #129746.