rust/src/test/ui/consts/const-blocks/trait-error.stderr

error[E0277]: the trait bound `Foo<String>: Copy` is not satisfied
  --> $DIR/trait-error.rs:5:5
   |
LL |     [Foo(String::new()); 4];
   |     ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `Foo<String>`
   |
   = help: the trait `Copy` is implemented for `Foo<T>`
   = note: the `Copy` trait is required because the repeated element will be copied

error: aborting due to 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 02:40:56 -05:00			error[E0277]: the trait bound `Foo<String>: Copy` is not satisfied
Remove const_in_array_rep_expr 2021-01-26 16:49:30 -06:00			`--> $DIR/trait-error.rs:5:5`
tests: Update and add tests for RFC 2203. 2019-06-12 02:46:56 -05:00			`\|`
			`LL \| [Foo(String::new()); 4];`
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			\| ^^^^^^^^^^^^^^^^^^^^^^^ the trait `Copy` is not implemented for `Foo<String>`
tests: Update and add tests for RFC 2203. 2019-06-12 02:46:56 -05:00			`\|`
Mention implementers of unsatisfied trait When encountering an unsatisfied trait bound, if there are no other suggestions, mention all the types that do implement that trait: ``` error[E0277]: the trait bound `f32: Foo` is not satisfied --> $DIR/impl_wf.rs:22:6 \| LL \| impl Baz<f32> for f32 { } \| ^^^^^^^^ the trait `Foo` is not implemented for `f32` \| = help: the following other types implement trait `Foo`: Option<T> i32 str note: required by a bound in `Baz` --> $DIR/impl_wf.rs:18:31 \| LL \| trait Baz<U: ?Sized> where U: Foo { } \| ^^^ required by this bound in `Baz` ``` Mention implementers of traits in `ImplObligation`s. Do not mention other `impl`s for closures, ranges and `?`. 2021-12-13 14:56:40 -06:00			= help: the trait `Copy` is implemented for `Foo<T>`
tests: Update and add tests for RFC 2203. 2019-06-12 02:46:56 -05:00			= note: the `Copy` trait is required because the repeated element will be copied

			`error: aborting due to previous error`

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