-
Notifications
You must be signed in to change notification settings - Fork 12.9k
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
ICE 1.73 nightly #115051
Comments
trait Q {
type S;
}
trait P {
type X: Q;
fn a(_: &<Self::X as Q>::S)
{
}
}
struct R<A>(A);
impl<E: Q, A> P for R<A>
where
A: P<X = E>,
{
type X = E;
fn a(_: &<Self::X as Q>::S)
{
}
} |
@rustbot label -I-prioritize +E-needs-bisection +regression-from-stable-to-nightly |
@sftse I'm afraid I can't reproduce the ICE with the provided MCVE. Can you post a bit more info on how to reproduce it? thanks @darklyspaced did you remove the @rustbot prioritize |
This is likely fixed by #115039. |
@apiraino I'm not familiar with the compiler development process, can you elaborate what issues could be preventing you from reproducing this? The rustc version is as stated, the dependency that triggered the ICE from which the MCVE was constructed is the chumsky crate. |
@sftse I've tried compiling the MCVE you provided in this comment by downloading the rustc version you indicated (1.73.0-nightly (28eb857 2023-08-12)) and then run:
Also attempted to bisect to earlier versions of rustc. On my Linux workstation that does not emit any ICE so clearly I'm missing some context. What's the correct command line you run to compile that MCVE to make it trigger the ICE? Unsure why you mention the "chumsky" crate, at a cursory look I don't identify how this is relevant here. Or is it? thanks |
@apiraino The commit you listed, of your rustc, does not match the commit I listed. It seems providing |
Triage: Let's close this issue in favor of the PR mentioned above. If the regression test added by it doesn't cover this case, please re-open! |
Code
Meta
Builds on
rustc --version --verbose
:ICE on
Error output
The text was updated successfully, but these errors were encountered: