Skip to content

Umbrella: Model the Drop trait #420

Description

@nikomatsakis

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:

  1. Type checking — enforce that Drop impls are "always applicable"
  2. Borrow checking — prevent partial moves from Drop types, insert implicit uses at scope exit
  3. Codegen — drop elaboration (what gets dropped, in what order)

The sub-issues are ordered roughly by dependency and difficulty.

Metadata

Metadata

Assignees

No one assigned

    Labels

    metaA tracking issue (an issue about issues)

    Type

    No type

    Projects

    Status
    Needs triage

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions