rust-lang / rust-lang/rust

Tracking Issue for immediately-aborting panics (currently -Cpanic=immediate-abort)

Open
#147,286 4 comments 5 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This is a tracking issue for the unstable panic strategy -Cpanic=immediate-abort, whose goal is to optimize for size, by not doing any panic message formatting or calling panic hooks, and perhaps exposing new optimizations along the way.

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.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

Steps
  • Select a name?
  • Declare stabilization?
Unresolved Questions
  • What should this flag be called?
Implementation history

https://github.com/rust-lang/rust/pull/55011
https://github.com/rust-lang/rust/pull/91737
https://github.com/rust-lang/rust/pull/104999
https://github.com/rust-lang/rust/pull/108924
https://github.com/rust-lang/rust/pull/117332
https://github.com/rust-lang/rust/pull/118362
https://github.com/rust-lang/rust/pull/129589
https://github.com/rust-lang/rust/pull/146317

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reviewing the implementation history in PRs #55011, #91737, #104999, #108924, #117332, #118362, #129589, and #146317, then read the linked stabilization guide. The tracking issue is complete when the flag has a selected name and stabilization has been declared.

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
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.