Tracking Issue for abort_immediate (abort in core)

Feature gate: #![feature(abort_immediate)]

This is a tracking issue for core::process::abort_immediate.

abort_immediate aborts/halts/crashes the process with as little overhead as possible. This exposes intrinsics::abort's behavior to stable. This is also reexported as std::process::abort_immediate.

Public API

// core::process
pub fn abort_immediate() -> !;

// std::process
pub fn abort_immediate() -> !;

Steps / History

(Remember to update the S-tracking-* label when checking boxes.)

• ACP: rust-lang/libs-team#442
• Implementation: rust-lang/rust#154604
• Final comment period (FCP)^1
• Stabilization PR

Unresolved Questions

• Given we want core::process::abort to opportunistically do std::process::abort if possible and abort_immediate otherwise, do we even want to expose a separate abort_immediate?
• Would another name more clearly communicate intent? Options include process::crash, process::halt, or others.

Start with the public API entries for core::process::abort_immediate and std::process::abort_immediate, then review the unresolved questions and completed implementation history. Done means resolving the API and naming concerns, completing the final comment period, and opening the stabilization PR.