Tracking Issue for `abort_unwind`
Open
Nobody has claimed this yet.
C-tracking-issue
T-libs
- Dominant language
- Rust
- Stars
- 119k
- Forks
- 16.1k
- PR merge metrics
- PR metrics pending
Description
Feature gate: #![feature(abort_unwind)]
This is a tracking issue for core::panic::abort_unwind.
abort_unwind is similar to catch_unwind, except that it aborts the process if it unwinds instead of catching the unwind. Prior to the abort, the panic hook is called in the same way that it is for other functions that cannot unwind (e.g. extern "C" fn).
Public API
// in core::panic (and std::panic)
fn abort_unwind<F: FnOnce() -> R, R>(f: F) -> R;
Steps / History
- ACP: https://github.com/rust-lang/libs-team/issues/441
- Implementation: https://github.com/rust-lang/rust/pull/130339
- Final naming (
abort_on_unwind)? - Improve documentation (add example)?
- Expose a better
fn abort() -> !incore? - Final comment period (FCP)^1
- Stabilization PR
Unresolved Questions
- None yet.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the implementation PR linked in the issue and the core::panic and std::panic entry points for abort_unwind. The tracking work is complete when naming, documentation, the core abort API question, final comment period, and stabilization are resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100