-
Notifications
You must be signed in to change notification settings - Fork 12.7k
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: 'Ok([Binder {..}, ...) is not fully resolved' #113846
Comments
Regressed from error in 1.65: https://rust.godbolt.org/z/ra4nMa31W @rustbot label regression-from-stable-to-stable |
probably duplicate of #103708 in some way? I have another 20-30 code snippets around thal all trigger the ice if anyone is interested |
Regressed in #98559. |
@lukas-code cool! how did trace back to that PR? I was bisecting but ended in this bunch of commits for nightly-2022-12-18
Same result for #103708. But now I suspect my results are wrong (the ICE blurb changed the output, maybe that's the reason) Tentatively closing in favor of #103708? |
@apiraino I got the same results at first, but none of the changes looked related. Then I manually checked nightly-2022-12-17 and saw that it still ICEed. I continued bisecting with this script: #!/bin/sh
E=$(cargo check 2>&1)
! grep "panicked" <<< "$E" ... and got these results:
Given the error message from https://rust.godbolt.org/z/ra4nMa31W, the |
WG-prioritization assigning priority (Zulip discussion). @rustbot label -I-prioritize +P-medium |
Reduced version copied from #132689: trait Www {
type W;
}
trait Xxx: Www<W = Self::X> {
type X;
}
trait Zzz<'a>: Xxx<X = Self::Z> {
type Z;
}
trait Bbb {}
impl<T> Bbb for T where T: for<'a> Zzz<'a> {} |
Code
The example will compile if the lifetime
'a
ofZzz
and all the associated HRTBs forZzz
are removed.Meta
Error occurs for both stable, beta, and nightly. Code was tested in the playground.
Tested Versions:
stable: rustc 1.71.0 (8ede3aa 2023-07-12) running on x86_64-unknown-linux-gnu
nightly: rustc 1.73.0-nightly (0e8e857 2023-07-16) running on x86_64-unknown-linux-gnu
Error output
Backtrace
The text was updated successfully, but these errors were encountered: