rust/tests/ui/async-await/async-error-span.rs

// edition:2018

// Regression test for issue #62382.

use std::future::Future;

fn get_future() -> impl Future<Output = ()> {
//~^ ERROR `()` is not a future
    panic!()
}

async fn foo() {
    let a; //~ ERROR type annotations needed
    get_future().await;
}

fn main() {}
Improve error span for async type inference error Fixes #62382 Previously, we would point at the spawn of the 'await' expression, instead of the actual expression with an unknown type. 2019-07-04 13:20:04 -05:00			`// edition:2018`

Remove async_await gates from tests. 2019-08-01 20:45:58 -05:00			`// Regression test for issue #62382.`
Improve error span for async type inference error Fixes #62382 Previously, we would point at the spawn of the 'await' expression, instead of the actual expression with an unknown type. 2019-07-04 13:20:04 -05:00
			`use std::future::Future;`

			`fn get_future() -> impl Future<Output = ()> {`
Adds a clearer message for when the async keyword is missing from a function Signed-off-by: Nell Shamrell <nellshamrell@gmail.com> 2020-06-18 12:30:47 -05:00			//~^ ERROR `()` is not a future
Improve error span for async type inference error Fixes #62382 Previously, we would point at the spawn of the 'await' expression, instead of the actual expression with an unknown type. 2019-07-04 13:20:04 -05:00			`panic!()`
			`}`

			`async fn foo() {`
Bless tests. 2023-06-24 05:02:54 -05:00			`let a; //~ ERROR type annotations needed`
Improve error span for async type inference error Fixes #62382 Previously, we would point at the spawn of the 'await' expression, instead of the actual expression with an unknown type. 2019-07-04 13:20:04 -05:00			`get_future().await;`
			`}`

			`fn main() {}`