rust/tests/ui/missing-trait-bounds/issue-69725.rs

// run-rustfix
// aux-build:issue-69725.rs
#![allow(dead_code)]

extern crate issue_69725;
use issue_69725::Struct;

fn crash<A>() {
    let _ = Struct::<A>::new().clone();
    //~^ ERROR: the method
}

fn main() {}
Suggest constraining `fn` type params when appropriate 2021-10-13 16:07:22 +00:00			`// run-rustfix`
Add a regression test 2020-03-07 04:38:50 +09:00			`// aux-build:issue-69725.rs`
Suggest constraining `fn` type params when appropriate 2021-10-13 16:07:22 +00:00			`#![allow(dead_code)]`
Add a regression test 2020-03-07 04:38:50 +09:00
			`extern crate issue_69725;`
			`use issue_69725::Struct;`

			`fn crash<A>() {`
			`let _ = Struct::<A>::new().clone();`
Avoid describing a method as 'not found' when bounds are unsatisfied Fixes #76267 When there is a single applicable method candidate, but its trait bounds are not satisfied, we avoid saying that the method is "not found". Insted, we update the error message to directly mention which bounds are not satisfied, rather than mentioning them in a note. 2020-09-26 17:20:14 -04:00			`//~^ ERROR: the method`
Add a regression test 2020-03-07 04:38:50 +09:00			`}`

			`fn main() {}`