-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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
internal compiler error: impossible case reached #52688
Comments
Can you provide a full repro case, as I am unable to reproduce the ICE with the supplied code. |
OK, I'll work on extracting the code that triggered this into a better repro case. |
Another case: https://travis-ci.org/dpc/rdedup/jobs/410594484 |
I hit this trying to $ cargo new --bin rust_52688_repro
Created binary (application) `rust_52688_repro` project
$ cd rust_52688_repro/
$ echo 'typenum = "=1.10.0"' >> Cargo.toml
$ cargo doc
Updating crates.io index
Compiling typenum v1.10.0
Documenting typenum v1.10.0
error: internal compiler error: librustc/traits/structural_impls.rs:178: impossible case reached
thread '<unnamed>' panicked at 'Box<Any>', librustc_errors/lib.rs:587:9
note: Run with `RUST_BACKTRACE=1` for a backtrace.
note: the compiler unexpectedly panicked. this is a bug.
note: we would appreciate a bug report: https://github.com/rust-lang/rust/blob/master/CONTRIBUTING.md#bug-reports
note: rustc 1.30.0 (da5f414c2 2018-10-24) running on x86_64-apple-darwin
error: Could not document `typenum`.
Caused by:
process didn't exit successfully: `rustdoc --crate-name typenum /Users/willglynn/.cargo/registry/src/github.com-1ecc6299db9ec823/typenum-1.10.0/src/lib.rs --cap-lints allow --color always -o /Users/delta407/rust/rust_52688_repro/target/doc -L dependency=/Users/willglynn/rust/rust_52688_repro/target/debug/deps` (exit code: 1) |
@willglynn: Duplicate of #53505 |
I can't reproduce this any more with latest nightlies. |
I think this issue can be closed. A related issue was fixed in #54199 and a regression test at |
rustc 1.29.0-nightly (6a1c063 2018-07-23) running on x86_64-apple-darwin
The below code has a bug (passing
&f
instead off
towait
) which should trigger a compilation error. The bug is that after printing the error the compiler panics.Compiler output (note that the above code is a simplified testcase; the actual error happens in an askama template)
The text was updated successfully, but these errors were encountered: