Tracking Issue for the Forget trait #165370

This is a tracking issue for the future#![feature(forget_trait)].
This is part of the "Immobile types and guaranteed destructors" project goal

Discussion around this issue earlier also took place on zulip at #t-lang/move-trait > Leak, Forget, and &own

About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however not meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps

• Create the feature gate Add Forget trait feature gate #165376
• Implement the feature
• Adjust documentation (see instructions on rustc-dev-guide)
• Style updates for any new syntax (nightly-style-procedure)
  • Style team decision on new formatting
  • Formatting for new syntax has been added to the Style Guide
  • (non-blocking) Formatting has been implemented in rustfmt
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

None, right now

Implementation history

There's already a tracking issue for the related Move trait. There is no implementation yet of this feature, but since it is part of a project goal, and I wanted to start adding an experimental implementation for it, this issue will track that work.