Stack overflow due to detected cycle when determining type not directly returned but still unambigous TAIT #140522
Labels
C-bug
Category: This is a bug.
F-type_alias_impl_trait
`#[feature(type_alias_impl_trait)]`
I-crash
Issue: The compiler crashes (SIGSEGV, SIGABRT, etc). Use I-ICE instead when the compiler panics.
S-has-mcve
Status: A Minimal Complete and Verifiable Example has been found for this issue
T-types
Relevant to the types team, which will review and decide on the PR/issue.
I tried this code:
I expected the compiler to be able to figure out the type alias
FooRet
because there is a singledefine_opaque
function, even if it doesn't directly return the type it's still unambiguous.Instead, the compiler wound up in a cycle trying to figure out the type, finally it gave the following
compile error:
Meta
Build using the Nightly version: 1.88.0-nightly (2025-04-29 7450913) from the playground.
Example on the Playground
The text was updated successfully, but these errors were encountered: