rust/tests/ui/async-await/in-trait/fn-not-async-err.rs

// edition: 2021

#![allow(incomplete_features)]

trait MyTrait {
    async fn foo(&self) -> i32;
}

impl MyTrait for i32 {
    fn foo(&self) -> i32 {
        //~^ ERROR: method `foo` should be async
        *self
    }
}

fn main() {}
Add tests for static async functions in traits This patch adds test cases for AFIT, the majority of which are currently expected to run as `check-fail`. 2022-10-04 01:27:11 +00:00			`// edition: 2021`

			`#![allow(incomplete_features)]`

			`trait MyTrait {`
			`async fn foo(&self) -> i32;`
			`}`

			`impl MyTrait for i32 {`
			`fn foo(&self) -> i32 {`
Ensure async trait impls are async (or otherwise return an opaque type) As a workaround for the full `#[refine]` semantics not being implemented yet, forbit returning a concrete future type like `Box<dyn Future>` or a manually implemented Future. `-> impl Future` is still permitted; while that can also cause accidental refinement, that's behind a different feature gate (`return_position_impl_trait_in_trait`) and that problem exists regardless of whether the trait method is async, so will have to be solved more generally. Fixes #102745 2022-11-03 00:45:08 +00:00			//~^ ERROR: method `foo` should be async
Add tests for static async functions in traits This patch adds test cases for AFIT, the majority of which are currently expected to run as `check-fail`. 2022-10-04 01:27:11 +00:00			`*self`
			`}`
			`}`

			`fn main() {}`