rust/tests/ui/async-await/issues/issue-63388-2.rs

//@ edition:2018

struct Xyz {
    a: u64,
}

trait Foo {}

impl Xyz {
    async fn do_sth<'a>(
        foo: &dyn Foo, bar: &'a dyn Foo
    ) -> &dyn Foo //~ ERROR missing lifetime specifier
    {
        foo
    }
}

fn main() {}
[AUTO-GENERATED] Migrate ui tests from `//` to `//@` directives 2024-02-16 20:02:50 +00:00			`//@ edition:2018`
revamp how we handle elision in async fn We now always make fresh lifetimne parameters for all elided lifetimes, whether they are in the inputs or outputs. But then we generate `'_` in the case of elided lifetimes from the outputs. Example: ```rust async fn foo<'a>(x: &'a u32) -> &u32 { .. } ``` becomes ```rust type Foo<'a, 'b> = impl Future<Output = &'b u32>; fn foo<'a>(x: &'a u32) -> Foo<'a, '_> ``` 2019-08-12 17:15:33 -04:00
			`struct Xyz {`
			`a: u64,`
			`}`

			`trait Foo {}`

			`impl Xyz {`
			`async fn do_sth<'a>(`
Update tests 2020-02-06 10:33:05 +01:00			`foo: &dyn Foo, bar: &'a dyn Foo`
revamp how we handle elision in async fn We now always make fresh lifetimne parameters for all elided lifetimes, whether they are in the inputs or outputs. But then we generate `'_` in the case of elided lifetimes from the outputs. Example: ```rust async fn foo<'a>(x: &'a u32) -> &u32 { .. } ``` becomes ```rust type Foo<'a, 'b> = impl Future<Output = &'b u32>; fn foo<'a>(x: &'a u32) -> Foo<'a, '_> ``` 2019-08-12 17:15:33 -04:00			`) -> &dyn Foo //~ ERROR missing lifetime specifier`
			`{`
			`foo`
			`}`
			`}`

			`fn main() {}`