-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
1.67 mir borrow checking ICE: thread 'rustc' panicked at 'region variables should not be hashed: '_#39r' #107505
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
Comments
Noratrieb
added
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
C-bug
Category: This is a bug.
labels
Jan 31, 2023
Still happens on nightly 2023-01-30. Entire ICE message
|
Reduced example: struct Command<'s> {
session: &'s (),
imp: std::convert::Infallible,
}
fn command(_: &()) -> Command<'_> {
unreachable!()
}
fn with_session<'s>(a: &std::process::Command, b: &'s ()) -> Command<'s> {
a.get_program();
command(b)
} command: My Rust version
|
It's because we need |
matthiaskrgr
added a commit
to matthiaskrgr/rust
that referenced
this issue
Feb 2, 2023
…ninhabited, r=jackh726 Erase regions before doing uninhabited check in borrowck ~Also, fingerprint query keys/values when debug assertions are enabled. This should make it easier to check for issues like this without `-Cincremental`, and make UI tests a bit cleaner.~ edit: moving that to a separate PR Fixes rust-lang#107505
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
This bug occurs in PR openssh-rust/openssh#112 when running
cargo check --all-targets --no-default-features
on the CI.Error messages:
The text was updated successfully, but these errors were encountered: