-
-
Notifications
You must be signed in to change notification settings - Fork 14.9k
Tracking Issue for abort_immediate (abort in core) #154601
Copy link
Copy link
Open
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.Status: The feature has not been implemented.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Metadata
Metadata
Assignees
Labels
C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFCCategory: An issue tracking the progress of sth. like the implementation of an RFCS-tracking-unimplementedStatus: The feature has not been implemented.Status: The feature has not been implemented.T-libs-apiRelevant to the library API team, which will review and decide on the PR/issue.Relevant to the library API team, which will review and decide on the PR/issue.
Type
Fields
Give feedbackNo fields configured for issues without a type.
Feature gate:
#![feature(abort_immediate)]This is a tracking issue for
core::process::abort_immediate.abort_immediateaborts/halts/crashes the process with as little overhead as possible. This exposesintrinsics::abort's behavior to stable. This is also reexported asstd::process::abort_immediate.Public API
Steps / History
(Remember to update the
S-tracking-*label when checking boxes.)Unresolved Questions
core::process::abortto opportunistically dostd::process::abortif possible andabort_immediateotherwise, do we even want to expose a separateabort_immediate?process::crash,process::halt, or others.Footnotes
https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html ↩