rust/tests/ui/async-await/issues/issue-55324.rs

//@ check-pass
//@ edition:2018

use std::future::Future;

async fn foo<F: Future<Output = i32>>(x: &i32, future: F) -> i32 {
    let y = future.await;
    *x + y
}

fn main() {}
Moving more build-pass tests to check-pass One or two tests became build-pass without the FIXME because they really needed build-pass (were failing without it). Helps with #62277 2020-04-19 17:27:28 -07:00			`//@ check-pass`
Refactor async fn return type lowering async fn now lowers directly to an existential type declaration rather than reusing the `impl Trait` return type lowering. As part of this, it lowers all argument-position elided lifetimes using the in-band-lifetimes machinery, creating fresh parameter names for each of them, using each lifetime parameter as a generic argument to the generated existential type. This doesn't currently successfully allow multiple argument-position elided lifetimes since `existential type` doesn't yet support multiple lifetimes where neither outlive the other. This requires a separate fix. 2019-03-13 17:42:23 -07:00			`//@ edition:2018`

			`use std::future::Future;`

			`async fn foo<F: Future<Output = i32>>(x: &i32, future: F) -> i32 {`
Reduce reliance on feature(await_macro). 2019-07-04 00:25:14 +02:00			`let y = future.await;`
Refactor async fn return type lowering async fn now lowers directly to an existential type declaration rather than reusing the `impl Trait` return type lowering. As part of this, it lowers all argument-position elided lifetimes using the in-band-lifetimes machinery, creating fresh parameter names for each of them, using each lifetime parameter as a generic argument to the generated existential type. This doesn't currently successfully allow multiple argument-position elided lifetimes since `existential type` doesn't yet support multiple lifetimes where neither outlive the other. This requires a separate fix. 2019-03-13 17:42:23 -07:00			`*x + y`
			`}`

			`fn main() {}`