rust/tests/ui/async-await/in-trait/async-example-desugared-boxed-in-trait.current.stderr

error[E0053]: method `foo` has an incompatible type for trait
  --> $DIR/async-example-desugared-boxed-in-trait.rs:17:28
   |
LL |     async fn foo(&self) -> i32 {
   |                            ^^^ expected `Pin<Box<dyn Future<Output = i32>>>`, found future
   |
note: type in trait
  --> $DIR/async-example-desugared-boxed-in-trait.rs:13:22
   |
LL |     fn foo(&self) -> Pin<Box<dyn Future<Output = i32> + '_>>;
   |                      ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   = note: expected signature `fn(&i32) -> Pin<Box<dyn Future<Output = i32>>>`
              found signature `fn(&i32) -> impl Future<Output = i32>`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0053`.
Add additional tests for static AFIT 2022-10-07 11:15:13 -05:00			error[E0053]: method `foo` has an incompatible type for trait
Run existing async in traits tests using -Zlower-impl-trait-in-trait-to-assoc-ty 2023-03-07 15:26:02 -06:00			`--> $DIR/async-example-desugared-boxed-in-trait.rs:17:28`
Add additional tests for static AFIT 2022-10-07 11:15:13 -05:00			`\|`
			`LL \| async fn foo(&self) -> i32 {`
fix: improve the suggestion on future not awaited Considering the following code ```rust fn foo() -> u8 { async fn async_fn() -> u8 { 22 } async_fn() } fn main() {} ``` the error generated before this commit from the compiler is ``` ➜ rust git:(macros/async_fn_suggestion) ✗ rustc test.rs --edition 2021 error[E0308]: mismatched types --> test.rs:4:5 \| 1 \| fn foo() -> u8 { \| -- expected `u8` because of return type ... 4 \| async_fn() \| ^^^^^^^^^^ expected `u8`, found opaque type \| = note: expected type `u8` found opaque type `impl Future<Output = u8>` help: consider `await`ing on the `Future` \| 4 \| async_fn().await \| ++++++ error: aborting due to previous error ``` In this case the error is nor perfect, and can confuse the user that do not know that the opaque type is the future. So this commit will propose (and conclude the work start in https://github.com/rust-lang/rust/issues/80658) to change the string `opaque type` to `future` when applicable and also remove the Expected vs Received note by adding a more specific one regarding the async function that return a future type. So the new error emitted by the compiler is ``` error[E0308]: mismatched types --> test.rs:4:5 \| 1 \| fn foo() -> u8 { \| -- expected `u8` because of return type ... 4 \| async_fn() \| ^^^^^^^^^^ expected `u8`, found future \| note: calling an async function returns a future --> test.rs:4:5 \| 4 \| async_fn() \| ^^^^^^^^^^ help: consider `await`ing on the `Future` \| 4 \| async_fn().await \| ++++++ error: aborting due to previous error ``` Signed-off-by: Vincenzo Palazzo <vincenzopalazzodev@gmail.com> 2023-02-10 12:03:54 -06:00			\| ^^^ expected `Pin<Box<dyn Future<Output = i32>>>`, found future
Add additional tests for static AFIT 2022-10-07 11:15:13 -05:00			`\|`
			`note: type in trait`
Run existing async in traits tests using -Zlower-impl-trait-in-trait-to-assoc-ty 2023-03-07 15:26:02 -06:00			`--> $DIR/async-example-desugared-boxed-in-trait.rs:13:22`
Add additional tests for static AFIT 2022-10-07 11:15:13 -05:00			`\|`
			`LL \| fn foo(&self) -> Pin<Box<dyn Future<Output = i32> + '_>>;`
			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
Mention signature rather than fn pointers when comparing impl/trait methods 2022-12-24 17:17:25 -06:00			= note: expected signature `fn(&i32) -> Pin<Box<dyn Future<Output = i32>>>`
			found signature `fn(&i32) -> impl Future<Output = i32>`
Add additional tests for static AFIT 2022-10-07 11:15:13 -05:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0053`.