-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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 with the newest nightly in lower_ty_direct
#60518
Comments
@Centril @jonas-schievink I've added the minimal case for reproducing. Hope that would help! |
Thanks! Looks like even this line is enough to trigger the ICE: async fn foo(ws: impl Iterator<Item = ()>) {} |
Another bug may be related: rustc complains you should have variable mut although it is already mut. |
That's #60498 and should be fixed in the next nightly |
cc @davidtwco it looks like the desugaring may have broken |
Oops, sorry. I'll take a look. |
Denominating since @davidtwco already has a fix |
@davidtwco @jonas-schievink Thanks guys! This is a super fast fix! |
Fix async fn lowering ICE with APIT. Fixes rust-lang#60518. This PR fixes an ICE where simple bindings (which aren't replaced with replacement arguments during async fn lowering) were not being visited in the def collector and thus caused an ICE during HIR lowering for types that use their `DefId` at that point - such as `impl Trait`. r? @cramertj
I was using nightly rust extensively for its async/await and specialization feature. After a recent update (nightly-2019-05-02), a new ICE introduced with following logs:
After a quick search it seems like this is the only
unwrap
in direct causelower_ty_direct
(stack frame 10).I cannot share the code or produce a minimal case because the code base is rather big.Minimal reproducing case
The text was updated successfully, but these errors were encountered: