rust/tests/ui/coherence/coherence-blanket-conflicts-with-specific-cross-crate.stderr

error[E0119]: conflicting implementations of trait `GoMut` for type `MyThingy`
  --> $DIR/coherence-blanket-conflicts-with-specific-cross-crate.rs:15:1
   |
LL | impl GoMut for MyThingy {
   | ^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: conflicting implementation in crate `go_trait`:
           - impl<G> GoMut for G
             where G: Go;

error: aborting due to previous error

For more information about this error, try `rustc --explain E0119`.
Don't print full paths in overlap errors 2022-11-10 04:21:11 +00:00			error[E0119]: conflicting implementations of trait `GoMut` for type `MyThingy`
Stabilize the `re_rebalance_coherence` feature 2019-10-26 17:28:02 +02:00			`--> $DIR/coherence-blanket-conflicts-with-specific-cross-crate.rs:15:1`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\|`
Add missing files 2018-12-29 02:13:06 +01:00			`LL \| impl GoMut for MyThingy {`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^`
			`\|`
			= note: conflicting implementation in crate `go_trait`:
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 10:40:56 +03:00			`- impl<G> GoMut for G`
			`where G: Go;`
Moved compile-fail tests to ui tests. 2018-08-08 14:28:26 +02:00
			`error: aborting due to previous error`

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