Tracking Issue for Interoperability With C++ Destruction Order

[pnkfelix]

This is a tracking issue for the MCP "Interoperability With C++ Destruction Order" (rust-lang/lang-team#135).

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.

Steps

• Implement the RFC (cc @rust-lang/lang -- can anyone write up mentoring
  instructions?)
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

• What is the right name for the attribute?
• There was much discussion about whether fine-grained control over drop order (e.g., drop_order(from_end) and drop_order(from_start)) or if even more flexible mechanisms (manually list out order for each field) is warranted here.
• should #[manually_drop] suppress destructuring?

Implementation history