Tracking Issue for __rust_no_alloc_shim_is_unstable

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 (done in https://github.com/rust-lang/rust/pull/86844)
• Adjust documentation (see instructions on rustc-dev-guide)
• Stabilization PR (see instructions on rustc-dev-guide)

Unresolved Questions

• Do we want to commit to allowing linking default output (rlib) format with arbitrary linkers? (see https://github.com/rust-lang/rust/pull/86844#issuecomment-1291008533)
• TODO, maybe more. Maybe we want some formal RFC etc. before stabilizing this.

Implementation history

• https://github.com/rust-lang/rust/pull/86844
  • default_alloc_error_handler became stable in https://github.com/rust-lang/rust/pull/102318

Start with the implementation history in PR #86844 and the rustc-dev-guide stabilization and documentation instructions linked in the issue. Determine the required documentation changes and resolve the listed question about linking rlib output with arbitrary linkers. Done means the documentation task and stabilization PR are complete.