Skip to content

Tracking Issue for abort_immediate (abort in core) #154601

@CAD97

Description

@CAD97

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.)

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.

Footnotes

  1. https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html

Metadata

Metadata

Assignees

No one assigned

    Labels

    C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions