Resolve Drop calls #1467
Draft
Resolve Drop calls #1467
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR makes it so we gather the data needed to know what code is called on a
dropterminator. To do this well, this adds an optionalresolve_drop_boundsoption (maybe this should be renamed) which addsT: Dropbounds to every possible generic parameter and associated type. This way, we can reuse the normalImplExprsystem. The one thing that's missing is the implicit Drop impls (so-called "drop glue") that exist for ADTs without an explicitimpl Drop; these are represented asDropData::Glue, and generating an adequateDropimpl is left as an exercice for the consumer. I'll see if I can get rustc to give me the right MIR automatically.Left as draft while I finish the charon side.