rust/tests/ui/traits/issue-71136.stderr

error[E0277]: the trait bound `Foo: Clone` is not satisfied
  --> $DIR/issue-71136.rs:5:5
   |
LL | #[derive(Clone)]
   |          ----- in this derive macro expansion
LL | struct FooHolster {
LL |     the_foos: Vec<Foo>,
   |     ^^^^^^^^^^^^^^^^^^ the trait `Clone` is not implemented for `Foo`, which is required by `Vec<Foo>: Clone`
   |
   = note: required for `Vec<Foo>` to implement `Clone`
   = note: this error originates in the derive macro `Clone` (in Nightly builds, run with -Z macro-backtrace for more info)
help: consider annotating `Foo` with `#[derive(Clone)]`
   |
LL + #[derive(Clone)]
LL | struct Foo(u8);
   |

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 `Foo: Clone` is not satisfied
Organize trait test files 2021-02-08 22:15:45 +00:00			`--> $DIR/issue-71136.rs:5:5`
Adding new test #71136 2020-05-03 09:11:23 +00:00			`\|`
Various diagnostics clean ups/tweaks * Always point at macros, including derive macros * Point at non-local items that introduce a trait requirement * On private associated item, point at definition 2021-07-17 18:13:50 +00:00			`LL \| #[derive(Clone)]`
			`\| ----- in this derive macro expansion`
			`LL \| struct FooHolster {`
Adding new test #71136 2020-05-03 09:11:23 +00:00			`LL \| the_foos: Vec<Foo>,`
Provide more context on derived obligation error primary label Expand the primary span of E0277 when the immediate unmet bound is not what the user wrote: ``` error[E0277]: the trait bound `i32: Bar` is not satisfied --> f100.rs:6:6 \| 6 \| <i32 as Foo>::foo(); \| ^^^ the trait `Bar` is not implemented for `i32`, which is required by `i32: Foo` \| help: this trait has no implementations, consider adding one --> f100.rs:2:1 \| 2 \| trait Bar {} \| ^^^^^^^^^ note: required for `i32` to implement `Foo` --> f100.rs:3:14 \| 3 \| impl<T: Bar> Foo for T {} \| --- ^^^ ^ \| \| \| unsatisfied trait bound introduced here ``` Fix #40120. 2024-01-29 18:31:02 +00:00			\| ^^^^^^^^^^^^^^^^^^ the trait `Clone` is not implemented for `Foo`, which is required by `Vec<Foo>: Clone`
Adding new test #71136 2020-05-03 09:11:23 +00:00			`\|`
Reword "Required because of the requirements on the impl of ..." 2022-08-15 20:31:37 +00:00			= note: required for `Vec<Foo>` to implement `Clone`
Show macro name in 'this error originates in macro' message When there are multiple macros in use, it can be difficult to tell which one was responsible for producing an error. 2021-02-13 19:52:25 +00:00			= note: this error originates in the derive macro `Clone` (in Nightly builds, run with -Z macro-backtrace for more info)
Suggest derivable trait on E0277 2022-03-31 14:58:45 +00:00			help: consider annotating `Foo` with `#[derive(Clone)]`
			`\|`
Tweak output for 'add line' suggestion 2023-03-18 02:18:39 +00:00			`LL + #[derive(Clone)]`
			`LL \| struct Foo(u8);`
Suggest derivable trait on E0277 2022-03-31 14:58:45 +00:00			`\|`
Adding new test #71136 2020-05-03 09:11:23 +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`
Adding new test #71136 2020-05-03 09:11:23 +00:00
			For more information about this error, try `rustc --explain E0277`.