Opaque Future Type crashed compiler :) Called Option::unwrap()
on a None
value
#141268
Labels
C-bug
Category: This is a bug.
I-ICE
Issue: The compiler panicked, giving an Internal Compilation Error (ICE) ❄️
S-needs-info
Status: The issue lacks details necessary to triage or act on it.
S-needs-repro
Status: This issue has no reproduction and needs a reproduction to make progress.
T-compiler
Relevant to the compiler team, which will review and decide on the PR/issue.
This is curiosity of our friends that will overthrow us AI :)
" The ICE is happening when the compiler tries to type-check
async fn foo(...) -> !
(and its call into the genericbar
) and ends up in a bustedreport_similar_impl_candidates
path.Code
Concretely, this signature:
—combined with your generic async method
—produces an opaque future type that the compiler can’t correctly resolve, and that eventually hits an internal
None.unwrap()
.Solution (work around -.-)
I explicitly defined the types (though i didn't want to) within the module that is being called. This no longer has the error because of that.
Meta
I'm using container...
Error output
Backtrace
The text was updated successfully, but these errors were encountered: