Explicitly reject negative and reservation drop impls #110859
Merged
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.
Fixes #110858
It doesn't really make sense for a type to have a
!Drop
impl. Or at least, I don't want us to implicitly assign a meaning to it by the way the compiler currently handles it (incompletely), and rather I would like to see a PR (or an RFC...) assign a meaning to!Drop
if we actually wanted one for it.