Skip to content
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

rustc suggests awaiting on non-future type on type mismatch with future #90931

Closed
edward-shen opened this issue Nov 15, 2021 · 1 comment · Fixed by #90933
Closed

rustc suggests awaiting on non-future type on type mismatch with future #90931

edward-shen opened this issue Nov 15, 2021 · 1 comment · Fixed by #90933
Labels
A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.

Comments

@edward-shen
Copy link
Contributor

Given the following code: playground

async fn foo() -> Result<(), ()> {
    todo!()
}

async fn bar() {
    let _unused = if true {
        foo()
    } else {
        foo().await
    };
    
    let _unused = match true {
        true => foo(),
        false => foo().await
    };
}

The current output is:

error[E0308]: `if` and `else` have incompatible types
  --> src/lib.rs:9:9
   |
6  |       let _unused = if true {
   |  ___________________-
7  | |         foo()
   | |         ----- expected because of this
8  | |     } else {
9  | |         foo().await
   | |         ^^^^^^^^^^^ expected opaque type, found enum `Result`
10 | |     };
   | |_____- `if` and `else` have incompatible types
   |
   = note: expected type `impl Future`
              found enum `Result<(), ()>`
help: consider `await`ing on the `Future`
   |
9  |         foo().await.await
   |                    ++++++

error[E0308]: `match` arms have incompatible types
  --> src/lib.rs:14:18
   |
12 |       let _unused = match true {
   |  ___________________-
13 | |         true => foo(),
   | |                 ----- this is found to be of type `impl Future`
14 | |         false => foo().await
   | |                  ^^^^^^^^^^^ expected opaque type, found enum `Result`
15 | |     };
   | |_____- `match` arms have incompatible types
   |
   = note: expected type `impl Future`
              found enum `Result<(), ()>`
help: consider `await`ing on the `Future`
   |
14 |         false => foo().await.await
   |                             ++++++

For more information about this error, try `rustc --explain E0308`.
error: could not compile `playground` due to 2 previous errors

Ideally the output should look like:

error[E0308]: `if` and `else` have incompatible types
  --> src/lib.rs:9:9
   |
6  |       let _unused = if true {
   |  ___________________-
7  | |         foo()
   | |         ----- expected because of this
8  | |     } else {
9  | |         foo().await
   | |         ^^^^^^^^^^^ expected opaque type, found enum `Result`
10 | |     };
   | |_____- `if` and `else` have incompatible types
   |
   = note: expected type `impl Future`
              found enum `Result<(), ()>`
help: consider `await`ing on the `Future`
   |
7  |         foo().await
   |              ++++++

error[E0308]: `match` arms have incompatible types
  --> src/lib.rs:14:18
   |
12 |       let _unused = match true {
   |  ___________________-
13 | |         true => foo(),
   | |                 ----- this is found to be of type `impl Future`
14 | |         false => foo().await
   | |                  ^^^^^^^^^^^ expected opaque type, found enum `Result`
15 | |     };
   | |_____- `match` arms have incompatible types
   |
   = note: expected type `impl Future`
              found enum `Result<(), ()>`
help: consider `await`ing on the `Future`
   |
13 |         false => foo().await
   |                       ++++++

For more information about this error, try `rustc --explain E0308`.
error: could not compile `playground` due to 2 previous errors

I've verified that this reproduces on Stable (1.56) and Nightly (1.58) on playground.

@edward-shen edward-shen added A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. labels Nov 15, 2021
@compiler-errors
Copy link
Member

I believe I found the bug in a match branch in rustc_infer::infer::error_reporting and I can put up a PR if my rustc build confirms it's actually where I think it is.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-diagnostics Area: Messages for errors, warnings, and lints T-compiler Relevant to the compiler team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants