-
Notifications
You must be signed in to change notification settings - Fork 13.3k
rustc nightly panics on refutable pattern #31561
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Labels
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
According to @arielb1 we used to block the use of refutable patterns in resolve, but it was changed, perhaps by @petrochenkov. @petrochenkov any thoughts? |
On further look, the error on old versions is an E0005 match error. Who's familiar with that? |
It seems like this is somehow caused by the changes to |
arielb1
added a commit
to arielb1/rust
that referenced
this issue
Mar 4, 2016
the assert was invalidated by PR rust-lang#31020 Fixes rust-lang#31561
This was referenced Mar 9, 2016
alexcrichton
pushed a commit
to alexcrichton/rust
that referenced
this issue
Mar 16, 2016
the assert was invalidated by PR rust-lang#31020 Fixes rust-lang#31561
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
regression-from-stable-to-nightly
Performance or correctness regression from stable to nightly.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
The below (invalid) code gives a panic in nightly rust. Stable and beta both happily reject it without panicking.
Seems to only happen when the enum has at least three arms. Changing number of arms the
(left == right)
seems to have left equal to number of arms minus one.The text was updated successfully, but these errors were encountered: