-
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 "... is not fully resolved'" with min_specialization and lifetime param #103708
Comments
😃 i'm glad that the assertion found something! worth investigating at least. i'll take a look at it, though I'm not exactly sure why Rust allows us to have an unconstrained lifetime parameter in the impl :/ (.. this is why) rust/compiler/rustc_hir_analysis/src/impl_wf_check.rs Lines 153 to 170 in 9565dfe
(maybe we can just hack it away by unifying unconstrained lifetime parameters to |
- rust-lang/rust#99173 - rust-lang/rust#103708 - rust-lang/rust#104827 - rust-lang/rust#105209 - rust-lang/rust#106298 - rust-lang/rust#106423 Signed-off-by: Yuki Okushi <jtitor@2k36.org> rust-lang/rust#99173 Signed-off-by: Yuki Okushi <jtitor@2k36.org>
Hah, looks like #116663 DID actually fix this 🙃 |
buy one get one free |
Also this should still ICE:
The root cause for this issue is not fixed. |
ah nvm, this one is fixed #103708 (comment) but
isnt
|
This ICEs with
#![feature(min_specialization)]
. Oddly enough, it does not ICE with#![feature(specialization)]
, which is supposedly more unstable.Found by fuzzing.
edited: New example, still failing after #116663 (thanks @matthiaskrgr)
Code
Error output
Full output with backtrace
Regression
Bisected to 6365e5a (#102903, @compiler-errors).
But that's just when the assertion was added.
Bisection details
searched nightlies: from nightly-2022-10-26 to nightly-2022-10-28
regressed nightly: nightly-2022-10-27
searched commit range: bed4ad6...1898c34
regressed commit: 6365e5a
bisected with cargo-bisect-rustc v0.6.4
Host triple: x86_64-apple-darwin
Version
rustc --version --verbose
:The text was updated successfully, but these errors were encountered: