This is an umbrella for modeling Drop in formality. There are multiple sub-issues of varying difficulty.
Sub-issues
Context
Modeling Drop correctly requires work across multiple layers:
- Type checking — enforce that Drop impls are "always applicable"
- Borrow checking — prevent partial moves from Drop types, insert implicit uses at scope exit
- Codegen — drop elaboration (what gets dropped, in what order)
The sub-issues are ordered roughly by dependency and difficulty.
This is an umbrella for modeling
Dropin formality. There are multiple sub-issues of varying difficulty.Sub-issues
#[may_dangle]/ dropck eyepatch #424 — Drop: model#[may_dangle]/ dropck eyepatchContext
Modeling Drop correctly requires work across multiple layers:
The sub-issues are ordered roughly by dependency and difficulty.