remove box_patterns#156749
Conversation
|
The parser was modified, potentially altering the grammar of (stable) Rust cc @fmease The Rustfmt subtree was changed cc @rust-lang/rustfmt The Clippy subtree was changed cc @rust-lang/clippy |
|
r? @Kivooeo rustbot has assigned @Kivooeo. Use Why was this reviewer chosen?The reviewer was selected based on:
|
|
The job Click to see the possible cause of the failure (guessed by this bot) |
Which one? would |
| } | ||
|
|
||
| fn main() { | ||
| let a = Box::new(Test::Foo(10)); |
There was a problem hiding this comment.
I suspect the spirit of the original test presumed having a and b boxed, so these should be kept as they were, and instead deref patterns should be used (implicitly or explicitly with deref!)? What do you think?
|
I don't expect the crater breakage to be significant; if it is, we should discuss again. @rfcbot merge lang |
|
Team member @tmandry has proposed to merge this. The next step is review by the rest of the tagged team members: Concerns: Once a majority of reviewers approve (and at most 2 approvals are outstanding), this will enter its final comment period. If you spot a major issue that hasn't been raised at any point in this process, please speak up! cc @rust-lang/lang-advisors: FCP proposed for lang, please feel free to register concerns. |
|
About to run crater. In my opinion check-only should be sufficient for this, do folks have other opinion? |
Yes, it's absolutely sufficient. This PR rejects previously valid code in the frontend of the compiler, it removes syntax. The only things that don't show up in check builds are monomorphization and codegen changes. IINM one thing which you miss out on in check-only crater runs are potential doctest regressions but that's just something you have to accept if you want to have "faster" crater runs, otherwise |
|
@bors try |
This comment has been minimized.
This comment has been minimized.
|
@craterbot run mode=check-only |
|
👌 Experiment ℹ️ Crater is a tool to run experiments across parts of the Rust ecosystem. Learn more |

This PR removes the old feature
box_patterns, tracked in #29641. As explained in #29641 (comment), this feature will not be stabilized sincederef_patterns(#87121) is a better and more general version of this feature.It was not possible to remove this feature until recently since the compiler itself still depended on this feature. This was changed with rust-lang/compiler-team#984.
This PR currently breaks crates that rely on box patterns using the incorrect pre-expansion feature gating (see #154045 for more details). Therefore, this needs a crater run.
Currently blocked on rust-lang/rust-clippy#17008.
Closes #29641.
Closes #105099.
Closes #156110.