480c4a18d5
Remove confusing 'while checking' note from opaque future type mismatches
Maybe I'm just misinterpreting the wording of the note. The only value I can see in this note is that it points out where the async's opaque future is coming from, but the way it's doing it is misleading IMO.
For example:
```rust
note: while checking the return type of the `async fn`
--> $DIR/dont-suggest-missing-await.rs:7:24
|
LL | async fn make_u32() -> u32 {
| ^^^ checked the `Output` of this `async fn`, found opaque type
```
We point at the type `u32` in the HIR, but then say "found opaque type". We also say "while checking"... but we're typechecking a totally different function when we get this type mismatch!
r? ``@estebank`` but feel free to reassign and/or take your time reviewing this. I'd be inclined to also discuss reworking the presentation of this type mismatch to restore some of these labels in a way that makes it more clear what it's trying to point out.
17 lines
546 B
Plaintext
17 lines
546 B
Plaintext
error[E0308]: mismatched types
|
|
--> $DIR/issue-99914.rs:9:27
|
|
|
|
|
LL | t.and_then(|t| -> _ { bar(t) });
|
|
| ^^^^^^ expected `Result<_, Error>`, found opaque type
|
|
|
|
|
= note: expected enum `Result<_, Error>`
|
|
found opaque type `impl Future<Output = ()>`
|
|
help: try wrapping the expression in `Ok`
|
|
|
|
|
LL | t.and_then(|t| -> _ { Ok(bar(t)) });
|
|
| +++ +
|
|
|
|
error: aborting due to previous error
|
|
|
|
For more information about this error, try `rustc --explain E0308`.
|