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

// Regression test for #65159. We used to ICE.
//
// edition:2018

async fn copy() -> Result<()>
//~^ ERROR enum takes 2 generic arguments
{
    Ok(()) //~ ERROR: type annotations needed
}

fn main() { }
don't assume we can always find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. 2019-10-09 08:50:39 -04:00			`// Regression test for #65159. We used to ICE.`
			`//`
			`// edition:2018`

Rework diagnostics for wrong number of generic args 2021-01-02 19:45:11 +01:00			`async fn copy() -> Result<()>`
diagnostics: remove inconsistent English article "this" from E0107 Consider `tests/ui/const-generics/generic_const_exprs/issue-102768.stderr`, the error message where it gives additional notes about where the associated type is defined, and how the dead code lint doesn't have an article, like in `tests/ui/lint/dead-code/issue-85255.stderr`. They don't have articles, so it seems unnecessary to have one here. 2023-02-23 10:27:06 -07:00			`//~^ ERROR enum takes 2 generic arguments`
don't assume we can always find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. 2019-10-09 08:50:39 -04:00			`{`
Avoid silencing relevant follow-up errors 2023-10-31 13:45:26 +00:00			`Ok(()) //~ ERROR: type annotations needed`
don't assume we can always find a return type hint in async fn In particular, we sometimes cannot if there is an earlier error. 2019-10-09 08:50:39 -04:00			`}`

			`fn main() { }`