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.
19 lines
637 B
Plaintext
19 lines
637 B
Plaintext
error[E0308]: mismatched types
|
|
--> $DIR/issue-102206.rs:6:27
|
|
|
|
|
LL | std::mem::size_of_val(foo());
|
|
| --------------------- ^^^^^
|
|
| | |
|
|
| | expected `&_`, found opaque type
|
|
| | help: consider borrowing here: `&foo()`
|
|
| arguments to this function are incorrect
|
|
|
|
|
= note: expected reference `&_`
|
|
found opaque type `impl Future<Output = ()>`
|
|
note: function defined here
|
|
--> $SRC_DIR/core/src/mem/mod.rs:LL:COL
|
|
|
|
error: aborting due to previous error
|
|
|
|
For more information about this error, try `rustc --explain E0308`.
|