Repository navigation
Control over Drop semantics #628
Description
| Metadata | |
|---|---|
| Contact | @JayanAXHF |
| Team(s) | compiler (@oli-obk), lang (@Nadrieril), opsem (@CAD97), types |
| Goal document | 2026/manually-drop-attr |
| Funding contact | Funding team |
Summary
Allow users to easily control the drop semantics of struct fields, letting them change drop order, and disable recursive destructors to make working with cross-language bindings easier.
- Allow cross-language bindings to expose struct fields without compatibility hazards, and
- Make all code that disables default destructor behavior more convenient to use in Rust.
This issue is intended for status updates only.
For general questions or comments, please contact a goal owner or post in the Zulip topic.
Activity
tomassedovic commentedon May 5, 2026
This issue is intended for status updates only.
For general questions or comments, please contact the owner(s) directly.
JayanAXHF commentedon Jul 3, 2026
Key developments: I have made a POC draft pull request with a rough implementation of the feature. Currently, we're finalising the semantics of something like this, how to structure the addition to the Destruct trait and whether the default implementation should be written straight to the function or if there should be a core intrinsic shim for for as Nadrieril suggested.
JayanAXHF commentedon Jul 28, 2026
No major updates right now. Life has kept my hands full. Really sorry about the slow pace here.
JayanAXHF commentedon Sep 5, 2026
Progress on the RFC draft thanks to Frances W.
JayanAXHF commentedon Oct 5, 2026
No major implementation updates right now. Design discussion continue in the zulip channel.