8000 Tracking Issue for immediately-aborting panics (currently -Cpanic=immediate-abort) · Issue #147286 · rust-lang/rust · GitHub 10000
[go: up one dir, main page]

Skip to content
  • Insights
  • Tracking Issue for immediately-aborting panics (currently -Cpanic=immediate-abort) #147286

    @saethlin

    Description

    @saethlin

    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

    #55011
    #91737
    #104999
    #108924
    #117332
    #118362
    #129589
    #146317

    Metadata

    Metadata

    Assignees

    No one assigned

      Labels

      C-tracking-issueCategory: An issue tracking the progress of sth. like the implementation of an RFC

      Type

      No type

      Projects

      No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        0