Repository navigation
ICE with higher order associated types #129372
Description
Activity
- addedC-bugCategory: This is a bug.Category: This is a bug.I-ICEIssue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️T-compilerRelevant to the compiler team, which will review and decide on the PR/issue.Relevant to the compiler team, which will review and decide on the PR/issue.
on Aug 21, 2024 - addedneeds-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triagingThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
on Aug 21, 2024 - addedA-associated-itemsArea: Associated items (types, constants & functions)Area: Associated items (types, constants & functions)
on Aug 21, 2024 Can be somewhat reproduced on stable with
pub fn into_vec<'inner>(dummy: impl FromRow<'inner>) { let _f = dummy.prepare(); } pub fn test() { into_vec(Assume(Some("test"))); } pub trait FromRow<'t> { type Out<'a>; fn prepare(self) -> impl for<'a> FnMut(&'a ()) -> Self::Out<'a>; } impl<'t, T: Value<'t>> FromRow<'t> for T where <T as Value<'t>>::Typ: MyTyp, { type Out<'a> = <T::Typ as MyTyp>::Out<'a>; fn prepare(self) -> impl for<'a> FnMut(&'a ()) -> Self::Out<'a> { move |_| loop {} } } pub struct Assume<A>(pub(crate) A); impl<'t, T, A: Value<'t, Typ = Option<T>>> Value<'t> for Assume<A> { type Typ = T; } pub trait Value<'t> { type Typ; } impl<'t> Value<'t> for &str { type Typ = String; } impl<'t, T: Value<'t, Typ = X>, X: MyTyp> Value<'t> for Option<T> { type Typ = Option<T::Typ>; } pub trait MyTyp: 'static { type Out<'t>; } impl MyTyp for String { type Out<'t> = Self; }
giving
WARN rustc_codegen_ssa::mir::locals Unexpected initial operand type: expected Closure(DefId(0:19 ~ unnamed_1[0fad]::{impl#0}::prepare::{closure#0}), [ReErased, Assume<s td::option::Option<&ReErased str>>, i16, Binder(extern "RustCall" fn((&ReBound(DebruijnIndex(0), BoundRegion { var: 0, kind: BrAnon }) (),)) -> Alias(Projection, AliasT y { args: [std::string::String, ReBound(DebruijnIndex(0), BoundRegion { var: 0, kind: BrAnon })], def_id: DefId(0:41 ~ unnamed_1[0fad]::MyTyp::Out) }), [Region(BrAnon)] ), ()]), found Closure(DefId(0:19 ~ unnamed_1[0fad]::{impl#0}::prepare::{closure#0}), [ReErased, Assume<std::option::Option<&ReErased str>>, i16, Binder(extern "RustCal l" fn((&ReBound(DebruijnIndex(0), BoundRegion { var: 0, kind: BrAnon }) (),)) -> std::string::String, [Region(BrAnon)]), ()]).See <https://github.com/rust-lang/rust/iss ues/114858>.(but no ICE)
warning links to #114858 and seems related although the setup is very different
It seems like this is a bug in normalization somewhere, but this specific ICE happens as part of getting debug info for types. So, building in release (or rather, without debug info) actually prevents the ICE but then still hits the same warning.
Slightly reduced:
fn into_vec(dummy: impl FromRow) { let _f = dummy.prepare(); } pub fn test() { into_vec(Assume(())); } trait FromRow { type Out<'a>; fn prepare(self) -> impl for<'a> FnMut(&'a ()) -> Self::Out<'a>; } impl<T: Value<Typ: MyTyp>> FromRow for T { type Out<'a> = <T::Typ as MyTyp>::Out<'a>; fn prepare(self) -> impl for<'a> FnMut(&'a ()) -> Self::Out<'a> { |_| loop {} } } struct Assume<A>(A); impl<T, A: Value<Typ = T>> Value for Assume<A> { type Typ = T; } trait Value { type Typ; } impl Value for () { type Typ = (); } trait MyTyp { type Out<'t>; } impl MyTyp for () { type Out<'t> = (); }
So I had my own smaller reproducer, but still bigger than @cyrgani. However, after seeing theirs, I minimized it further similar to @cyrgani's version, except some of my comments might be useful. They're based on tracing the right parts of the compiler:
pub struct Wrapper<T>(T); struct Struct; pub trait TraitA { // NEEDS TO BE GAT type AssocA<'t>; } pub trait TraitB { type AssocB; } pub fn helper(v: impl MethodTrait) { // monomorphization instantiates something it then normalizes to: // // Closure( // DefId(0:27 ~ unnamed_1[00e7]::{impl#0}::method::{closure#0}), // [ // Wrapper1<StructX>, // i16, // Binder { // value: extern "RustCall" fn((&'^0 (),)) -> Alias(Projection, AliasTy { args: [StructX, '^0], def_id: DefId(0:10 ~ unnamed_1[00e7]::TraitA::AssocA), .. }), // bound_vars: [Region(BrAnon)] // }, // () // ] // ), // // This should be completely normalized but isn't. // so, normalizing again gives (StructX is inserted) for // Alias(Projection, AliasTy { args: [StructX, '^0], def_id: DefId(0:10 ~ unnamed_1[00e7]::TraitA::AssocA), .. }) // // Closure( // DefId(0:27 ~ unnamed_1[00e7]::{impl#0}::method::{closure#0}), // [ // Wrapper1<StructX>, // i16, // Binder { // value: extern "RustCall" fn((&'^0 (),)) -> StructX, bound_vars: [Region(BrAnon)] // }, // () // ] // ). let _local_that_causes_ice = v.method(); } pub fn main() { helper(Wrapper(Struct)); } pub trait MethodTrait { type Assoc<'a>; fn method(self) -> impl for<'a> FnMut(&'a ()) -> Self::Assoc<'a>; } impl<T: TraitB> MethodTrait for T where <T as TraitB>::AssocB: TraitA, { type Assoc<'a> = <T::AssocB as TraitA>::AssocA<'a>; // must be a method (through Self), the example below doesn't work (as a standalone function) // fn helper2<M: MethodTrait>(_v: M) -> impl for<'a> FnMut(&'a ()) -> M::Assoc<'a> { // move |_| loop {} // } fn method(self) -> impl for<'a> FnMut(&'a ()) -> Self::Assoc<'a> { move |_| loop {} } } impl<T, B> TraitB for Wrapper<B> where B: TraitB<AssocB = T>, { type AssocB = T; } impl TraitB for Struct { type AssocB = Struct; } impl TraitA for Struct { type AssocA<'t> = Self; }
So the specific ICE, like I said before, is essentially unrelated. It's because some debug assertion got changed into an actual assertion here. The problem is actually easier to see when you don't look at this assertion, but wait until the same root cause causes a warning later in the compiler when a sanity check is done here.
What's going on is that the warning triggers when the initialization of a MIR local doesn't match the type of its declaration. In this case we're talking about a ZST function item, and in that codepath, to get the type of the function item at the declaration site, the declaration type is monomorphized, and then
layout_ofis used. Bothmonomorphizeandlayout_ofnormalize, so the type is normalized twice.However, to check for the warning the type is only monomorphized, causing only one normalization: here
As I show in my comment in the code example, the monomorphized type normalized once gives:
Closure( DefId(0:27 ~ unnamed_1[00e7]::{impl#0}::method::{closure#0}), [ Wrapper1<StructX>, i16, Binder { value: extern "RustCall" fn((&'^0 (),)) -> Alias(Projection, AliasTy { args: [StructX, '^0], def_id: DefId(0:10 ~ unnamed_1[00e7]::TraitA::AssocA), .. }), bound_vars: [Region(BrAnon)] }, () ] ),and the second normalization gives:
Closure( DefId(0:27 ~ unnamed_1[00e7]::{impl#0}::method::{closure#0}), [ Wrapper1<StructX>, i16, Binder { value: extern "RustCall" fn((&'^0 (),)) -> StructX, bound_vars: [Region(BrAnon)] }, () ] )which, notably, is different!
For some reason the first normalization round, rust is happy to normalize to something still containing a Projection which is normalized away in round two.
In the assertion that causes the ICE, essentially the same happens. The compiler sees if normalizing is idempotent and doesn't change the type anymore, but it still does.
Well, I thought I tried this at the start, but apparently not. Dumb me, whatever. The next solver (#107374) fixes all this so this will soon be a non-issue.
Try it with
RUSTFLAGS="-Znext-solver"- added a commit that references this issue
on Sep 8, 2024 @rustbot label +S-bug-has-test
- addedS-bug-has-testStatus: This bug is tracked inside the repo by a `known-bug` test.Status: This bug is tracked inside the repo by a `known-bug` test.
on Sep 8, 2024 - addedfixed-by-next-solverFixed by the next-generation trait solver, `-Znext-solver`.Fixed by the next-generation trait solver, `-Znext-solver`.A-GATsArea: Generic associated types (GATs)Area: Generic associated types (GATs)
on Sep 24, 2024 - removedneeds-triageThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triagingThis issue may need triage. Remove when done. See docs forge.rust-lang.org/release/issue-triaging
on Sep 24, 2024 I'm working on #139088 and noted that as a side effect this test doesn't ICE anymore in my PR. Same happens with @saethlin's #131650 I guess on both cases probably due to pushing monomorphization earlier but I did not investigate properly.
Do we have ui tests for this that test only the new solver?.
This doesn’t ICE any more, neither with
-Znext-solver, nor without it.It seems to have been fixed in #139088, which is also where the crash test from this test got removed. I wonder if it should have been kept in instead, but if not, then this issue can be closed, I suppose. @spastorino, what do you think?
- addedE-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.Call for participation: An issue has been fixed and does not reproduce, but no test has been added.
on Apr 24, 2026 @jakubadamw would you want to go ahead and add a regression test for this?
Reacted by teor and Jacob Adam@spastorino, sorry, I missed this comment back then! Yes, I included it in #160407. 🙂
Oh dear, I double-checked, and this is, in fact, not fixed yet. I got confused by the fact that a crash test for this issue had once been removed, but it seems to have been a matter of that particular test’s compilation flags. In #160407 I’m about to add a crash test that still reproduces the ICE.
@rustbot labels -E-needs-test
- removedE-needs-testCall for participation: An issue has been fixed and does not reproduce, but no test has been added.Call for participation: An issue has been fixed and does not reproduce, but no test has been added.
on Aug 3, 2026 - added a commit that references this issue
on Sep 20, 2026 - added a commit that references this issue
on Oct 8, 2026
Code
Meta
rustc --version --verbose:Error output
Backtrace
rustc-ice-2024-08-21T20_21_27-40569.txt