rust/tests/ui/error-should-say-copy-not-pod.stderr

error[E0277]: the trait bound `String: Copy` is not satisfied
  --> $DIR/error-should-say-copy-not-pod.rs:6:17
   |
LL |     check_bound("nocopy".to_string());
   |     ----------- ^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `String`
   |     |
   |     required by a bound introduced by this call
   |
note: required by a bound in `check_bound`
  --> $DIR/error-should-say-copy-not-pod.rs:3:18
   |
LL | fn check_bound<T:Copy>(_: T) {}
   |                  ^^^^ required by this bound in `check_bound`
help: consider removing this method call, as the receiver has type `&'static str` and `&'static str: Copy` trivially holds
   |
LL -     check_bound("nocopy".to_string());
LL +     check_bound("nocopy");
   |

error: aborting due to 1 previous error

For more information about this error, try `rustc --explain E0277`.
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 07:40:56 +00:00			error[E0277]: the trait bound `String: Copy` is not satisfied
When possible point at argument causing item obligation failure 2019-09-16 04:58:20 +00:00			`--> $DIR/error-should-say-copy-not-pod.rs:6:17`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| check_bound("nocopy".to_string());`
Point at call span that introduced obligation for the arg 2021-09-07 11:30:53 +00:00			\| ----------- ^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `String`
			`\| \|`
			`\| required by a bound introduced by this call`
Use note to point at bound introducing requirement 2021-07-31 16:26:55 +00:00			`\|`
			note: required by a bound in `check_bound`
			`--> $DIR/error-should-say-copy-not-pod.rs:3:18`
			`\|`
			`LL \| fn check_bound<T:Copy>(_: T) {}`
			\| ^^^^ required by this bound in `check_bound`
Detect when method call on argument could be removed to fulfill failed trait bound When encountering ```rust struct Foo; struct Bar; impl From<Bar> for Foo { fn from(_: Bar) -> Self { Foo } } fn qux(_: impl From<Bar>) {} fn main() { qux(Bar.into()); } ``` Suggest removing `.into()`: ``` error[E0283]: type annotations needed --> f100.rs:8:13 \| 8 \| qux(Bar.into()); \| --- ^^^^ \| \| \| required by a bound introduced by this call \| = note: cannot satisfy `_: From<Bar>` note: required by a bound in `qux` --> f100.rs:6:16 \| 6 \| fn qux(_: impl From<Bar>) {} \| ^^^^^^^^^ required by this bound in `qux` help: try using a fully qualified path to specify the expected types \| 8 \| qux(<Bar as Into<T>>::into(Bar)); \| +++++++++++++++++++++++ ~ help: consider removing this method call, as the receiver has type `Bar` and `Bar: From<Bar>` can be fulfilled \| 8 - qux(Bar.into()); 8 + qux(Bar); \| ``` Fix #71252 2024-02-14 17:48:40 +00:00			help: consider removing this method call, as the receiver has type `&'static str` and `&'static str: Copy` trivially holds
			`\|`
			`LL - check_bound("nocopy".to_string());`
			`LL + check_bound("nocopy");`
			`\|`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
Show number in error message even for one error Co-authored-by: Adrian <adrian.iosdev@gmail.com> 2023-11-21 15:44:16 +00:00			`error: aborting due to 1 previous error`
Moved compile-fail tests to ui tests. 2018-08-08 12:28:26 +00:00
			For more information about this error, try `rustc --explain E0277`.