rust/tests/ui/error-codes/e0119/issue-23563.stderr

error[E0119]: conflicting implementations of trait `LolFrom<&[_]>` for type `LocalType<_>`
  --> $DIR/issue-23563.rs:13:1
   |
LL | impl<'a, T> LolFrom<&'a [T]> for LocalType<T> {
   | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: conflicting implementation in crate `issue_23563_a`:
           - impl<T, U> LolFrom<T> for U
             where T: LolInto<U>;

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-09 22:21:11 -06:00			error[E0119]: conflicting implementations of trait `LolFrom<&[_]>` for type `LocalType<_>`
Remove licenses 2018-12-25 09:56:47 -06:00			`--> $DIR/issue-23563.rs:13:1`
Print the conflicting impl on E0119 with external crate. 2017-10-22 10:14:53 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06:00			`LL \| impl<'a, T> LolFrom<&'a [T]> for LocalType<T> {`
Use def span for conflicting impls and recursive fn 2017-12-18 01:46:55 -06:00			`\| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^`
Print the conflicting impl on E0119 with external crate. 2017-10-22 10:14:53 -05:00			`\|`
			= note: conflicting implementation in crate `issue_23563_a`:
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			`- impl<T, U> LolFrom<T> for U`
			`where T: LolInto<U>;`
Print the conflicting impl on E0119 with external crate. 2017-10-22 10:14:53 -05:00
			`error: aborting due to previous error`

update tests 2018-03-03 08:59:40 -06:00			For more information about this error, try `rustc --explain E0119`.