rust-lang / rust-lang/rust

Remove edition-dependent behavior on `panic`

Open
#151,084 14 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

A-edition-2027 A-maybe-future-edition I-edition-nominated I-edition-radar I-lang-radar T-edition T-lang
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

As @ehuss said:

It wasn't clear to me before this was merged that this approved a change for the 2026 edition. Can we remove that edition check and go through the process for adding new features to an edition? (Or, preferably, if this ends up changing for all editions, then there will be no additional work to do.)

Originally posted by @ehuss in https://github.com/rust-lang/rust/issues/139493#issuecomment-3746618349

Let's please remove the edition-dependent behavior until we separately accept this within a future edition.

cc @rust-lang/edition

Related

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 related pull request #139493 and issue #147319 to locate the edition check affecting panic. The work is done when the edition-dependent behavior is removed without bundling approval for a future edition; consult the Rust edition process and reference pull request #2077 for related context.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
compilers
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.