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

error[E0599]: the method `clone` exists for struct `Struct<A>`, but its trait bounds were not satisfied
  --> $DIR/issue-69725.rs:9:32
   |
LL |     let _ = Struct::<A>::new().clone();
   |                                ^^^^^ method cannot be called on `Struct<A>` due to unsatisfied trait bounds
   |
  ::: $DIR/auxiliary/issue-69725.rs:2:1
   |
LL | pub struct Struct<A>(A);
   | -------------------- doesn't satisfy `Struct<A>: Clone`
   |
   = note: the following trait bounds were not satisfied:
           `A: Clone`
           which is required by `Struct<A>: Clone`
help: consider restricting the type parameter to satisfy the trait bound
   |
LL | fn crash<A>() where A: Clone {
   |               ++++++++++++++

error: aborting due to previous error

For more information about this error, try `rustc --explain E0599`.
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 16:20:14 -05:00			error[E0599]: the method `clone` exists for struct `Struct<A>`, but its trait bounds were not satisfied
Suggest constraining `fn` type params when appropriate 2021-10-13 11:07:22 -05:00			`--> $DIR/issue-69725.rs:9:32`
Add a regression test 2020-03-06 13:38:50 -06:00			`\|`
			`LL \| 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 16:20:14 -05:00			\| ^^^^^ method cannot be called on `Struct<A>` due to unsatisfied trait bounds
Remove trailing whitespace from error messages 2021-06-10 06:52:00 -05:00			`\|`
Add a regression test 2020-03-06 13:38:50 -06:00			`::: $DIR/auxiliary/issue-69725.rs:2:1`
			`\|`
			`LL \| pub struct Struct<A>(A);`
Shorten def_span for more items. 2022-02-13 09:27:59 -06:00			\| -------------------- doesn't satisfy `Struct<A>: Clone`
Add a regression test 2020-03-06 13:38:50 -06:00			`\|`
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 16:20:14 -05:00			`= note: the following trait bounds were not satisfied:`
pretty: trim paths of unique symbols If a symbol name can only be imported from one place for a type, and as long as it was not glob-imported anywhere in the current crate, we can trim its printed path and print only the name. This has wide implications on error messages with types, for example, shortening `std::vec::Vec` to just `Vec`, as long as there is no other `Vec` importable anywhere. This adds a new '-Z trim-diagnostic-paths=false' option to control this feature. On the good path, with no diagnosis printed, we should try to avoid issuing this query, so we need to prevent trimmed_def_paths query on several cases. This change also relies on a previous commit that differentiates between `Debug` and `Display` on various rustc types, where the latter is trimmed and presented to the user and the former is not. 2020-09-02 02:40:56 -05:00			`A: Clone`
			which is required by `Struct<A>: Clone`
Suggest constraining `fn` type params when appropriate 2021-10-13 11:07:22 -05:00			`help: consider restricting the type parameter to satisfy the trait bound`
			`\|`
			`LL \| fn crash<A>() where A: Clone {`
			`\| ++++++++++++++`
Add a regression test 2020-03-06 13:38:50 -06:00
			`error: aborting due to previous error`

			For more information about this error, try `rustc --explain E0599`.