ice: args contain late-bound region at index 0 which can't be normalized
#11230
Comments
matthiaskrgr
added
C-bug
|
|
Minimized: fn main() {
const A: &[for<'a> fn(&'a ())] = &[];
for v in A.iter() {}
} |
|
Some more context (I wrote this yesterday but forgot to actually submit the comment). This ICE happened in the
The actual "problematic" bit in the I looked around for clippy lints that "misuse" trait Helper<'a>: Iterator<Item = fn()> {}
fn x(w: &mut dyn for<'a> Helper<'a>) {
w.collect::<Vec<_>>().is_empty();
}It seems to be trying to do the projection |
|
I'm not sure if this is a bug in rustc or not. |
bors
added a commit
that referenced
this issue
Nov 12, 2023
Don't check for late-bound vars, check for escaping bound vars Fixes an assertion that didn't make sense. Many valid and well-formed types *have* late-bound vars (e.g. `for<'a> fn(&'a ())`), they just must not have *escaping* late-bound vars in order to be normalized correctly. Addresses #11230, cc `@jyn514` and `@matthiaskrgr`
bors
added a commit
that referenced
this issue
Nov 12, 2023
Don't check for late-bound vars, check for escaping bound vars Fixes an assertion that didn't make sense. Many valid and well-formed types *have* late-bound vars (e.g. `for<'a> fn(&'a ())`), they just must not have *escaping* late-bound vars in order to be normalized correctly. Addresses #11230, cc `@jyn514` and `@matthiaskrgr` changelog: don't check for late-bound vars, check for escaping bound vars. Addresses #11230
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Dec 21, 2023
Don't check for late-bound vars, check for escaping bound vars Fixes an assertion that didn't make sense. Many valid and well-formed types *have* late-bound vars (e.g. `for<'a> fn(&'a ())`), they just must not have *escaping* late-bound vars in order to be normalized correctly. Addresses rust-lang/rust-clippy#11230, cc `@jyn514` and `@matthiaskrgr` changelog: don't check for late-bound vars, check for escaping bound vars. Addresses rust-lang/rust-clippy#11230
flip1995
pushed a commit
to flip1995/rust
that referenced
this issue
Dec 21, 2023
Don't check for late-bound vars, check for escaping bound vars Fixes an assertion that didn't make sense. Many valid and well-formed types *have* late-bound vars (e.g. `for<'a> fn(&'a ())`), they just must not have *escaping* late-bound vars in order to be normalized correctly. Addresses rust-lang/rust-clippy#11230, cc `@jyn514` and `@matthiaskrgr` changelog: don't check for late-bound vars, check for escaping bound vars. Addresses rust-lang/rust-clippy#11230
xobs
pushed a commit
to betrusted-io/rust
that referenced
this issue
Dec 24, 2023
Don't check for late-bound vars, check for escaping bound vars Fixes an assertion that didn't make sense. Many valid and well-formed types *have* late-bound vars (e.g. `for<'a> fn(&'a ())`), they just must not have *escaping* late-bound vars in order to be normalized correctly. Addresses rust-lang/rust-clippy#11230, cc `@jyn514` and `@matthiaskrgr` changelog: don't check for late-bound vars, check for escaping bound vars. Addresses rust-lang/rust-clippy#11230
|
Is this fixed by #11760? |
LucasSte
pushed a commit
to LucasSte/rust
that referenced
this issue
Feb 19, 2024
Don't check for late-bound vars, check for escaping bound vars Fixes an assertion that didn't make sense. Many valid and well-formed types *have* late-bound vars (e.g. `for<'a> fn(&'a ())`), they just must not have *escaping* late-bound vars in order to be normalized correctly. Addresses rust-lang/rust-clippy#11230, cc `@jyn514` and `@matthiaskrgr` changelog: don't check for late-bound vars, check for escaping bound vars. Addresses rust-lang/rust-clippy#11230
matthiaskrgr
added a commit
to matthiaskrgr/rust-clippy
that referenced
this issue
Dec 31, 2024
matthiaskrgr
added a commit
to matthiaskrgr/rust-clippy
that referenced
this issue
Dec 31, 2024
Closes rust-lang#11230 changelog: nonew.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Summary
while checking rustc_query_impl
The text was updated successfully, but these errors were encountered: