Control over Drop semantics

[tomassedovic]

Metadata
Point of contact	@JayanAXHF
Team(s)	compiler, lang, opsem, types
Goal document	2026/manually-drop-attr

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.

Tasks and status

---

Note: we have updated the body to match the 2026 goal. Your original text is preserved below.

Details

Metadata
Point of contact	@thunderseethe
Team(s)	compiler, lang, opsem, types
Goal document	2026/manually-drop-attr

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.

Tasks and status

[tomassedovic]

This issue is intended for status updates only.

For general questions or comments, please contact the owner(s) directly.

[JayanAXHF]

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]

No major updates right now. Life has kept my hands full. Really sorry about the slow pace here.