-
Notifications
You must be signed in to change notification settings - Fork 13.3k
ICE: sty: None
#138361
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
Comments
mvce probably fn a() {
[0; loop{}];
std::mem::transmute(4)
}
fn main() {} |
bisects to nightly-2024-02-23 |
bisecting between nightly-2024-02-22 and nightly-2024-02-23 |
bisection reports: 46f4983 is the first bad commit cc @nnethercote
|
Interestingly the panic I'm getting is different:
|
It seems that in both cases, what happens is that an |
I think what's going on here is that the "constant evaluation is taking a long time" lint is getting triggered, aborts the typechecking of the function, and then the transmute lint trips over that – and because the former is a lint, it isn't enough for the lint passes to decide "this thing is broken enough that we shouldn't try to lint it"? Not sure where is the code that actually implements this, though, and no idea why @nnethercote's commit would change this behavior. |
Okay, before the offending commit, an actual typechecking error gets emitted in addition to the
|
@rustbot claim |
@rustbot unclaim |
cough @rustbot release-assignment |
snippet:
Version information
Possibly related line of code:
rust/compiler/rustc_middle/src/ty/sty.rs
Lines 2072 to 2084 in ebf0cf7
Command:
/home/matthias/.rustup/toolchains/master/bin/rustc
Program output
The text was updated successfully, but these errors were encountered: