-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Nightly async fn ICE #65159
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Comments
@nikomatsakis this commit seems the one to blame. rust/src/librustc_typeck/check/closure.rs Lines 681 to 692 in 0358617
tested the snippet above with RUSTC_LOG=rustc_typeck::check=debug , rustc complained:
RUSTC_LOG=rustc_typeck::check=debugerror[E0107]: wrong number of type arguments: expected 2, found 1 --> t.rs:3:19 | 3 | async fn foo() -> std::result::Result<()> { | ^^^^^^^^^^^^^^^^^^^^^^^ expected 2 type arguments[DEBUG rustc_typeck::check] check_fn(sig=([]; c_variadic: false)->impl std::future::Future, fn_id=HirId { owner: DefIndex(13), local_id: 0 }, param_env=ParamEnv { caller_bounds: [], reveal: UserFacing, def_id: None }) |
I'll investigate tomorrow. |
Pending fix in #65235 |
…eturn-ice, r=cramertj don't assume we can *always* find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. Fixes rust-lang#65159 r? @cramertj, who reviewed the original PR
…eturn-ice, r=cramertj don't assume we can *always* find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. Fixes rust-lang#65159 r? @cramertj, who reviewed the original PR
…eturn-ice, r=cramertj don't assume we can *always* find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. Fixes rust-lang#65159 r? @cramertj, who reviewed the original PR
The following ICE's in nightly:
Backtrace:
Beta just errors normally, complaining that
Result
takes two parameters.The text was updated successfully, but these errors were encountered: