rust/tests/ui/error-codes/e0119/conflict-with-std.stderr

error[E0119]: conflicting implementations of trait `AsRef<Q>` for type `Box<Q>`
  --> $DIR/conflict-with-std.rs:5:1
   |
LL | impl AsRef<Q> for Box<Q> {
   | ^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: conflicting implementation in crate `alloc`:
           - impl<T, A> AsRef<T> for Box<T, A>
             where A: Allocator, T: ?Sized;

error[E0119]: conflicting implementations of trait `From<S>` for type `S`
  --> $DIR/conflict-with-std.rs:12:1
   |
LL | impl From<S> for S {
   | ^^^^^^^^^^^^^^^^^^
   |
   = note: conflicting implementation in crate `core`:
           - impl<T> From<T> for T;

error[E0119]: conflicting implementations of trait `TryFrom<X>` for type `X`
  --> $DIR/conflict-with-std.rs:19:1
   |
LL | impl TryFrom<X> for X {
   | ^^^^^^^^^^^^^^^^^^^^^
   |
   = note: conflicting implementation in crate `core`:
           - impl<T, U> TryFrom<U> for T
             where U: Into<T>;

error: aborting due to 3 previous errors

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 `AsRef<Q>` for type `Box<Q>`
Update ui tests 2019-04-22 11:30:54 -05:00			`--> $DIR/conflict-with-std.rs:5: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 AsRef<Q> for Box<Q> {`
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 `alloc`:
Support custom allocators in `Box` Remove `Box::leak_with_alloc` Add leak-test for box with allocator Rename `AllocErr` to `AllocError` in leak-test Add `Box::alloc` and adjust examples to use the new API 2020-10-06 09:37:23 -05:00			`- impl<T, A> AsRef<T> for Box<T, A>`
Rename `AllocRef` to `Allocator` and `(de)alloc` to `(de)allocate` 2020-12-04 07:47:15 -06:00			`where A: Allocator, T: ?Sized;`
Print the conflicting impl on E0119 with external crate. 2017-10-22 10:14:53 -05:00
Don't print full paths in overlap errors 2022-11-09 22:21:11 -06:00			error[E0119]: conflicting implementations of trait `From<S>` for type `S`
Update ui tests 2019-04-22 11:30:54 -05:00			`--> $DIR/conflict-with-std.rs:12: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 From<S> for S {`
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 `core`:
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> From<T> for T;`
Print the conflicting impl on E0119 with external crate. 2017-10-22 10:14:53 -05:00
Don't print full paths in overlap errors 2022-11-09 22:21:11 -06:00			error[E0119]: conflicting implementations of trait `TryFrom<X>` for type `X`
Update ui tests 2019-04-22 11:30:54 -05:00			`--> $DIR/conflict-with-std.rs:19: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 TryFrom<X> for X {`
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 `core`:
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> TryFrom<U> for T`
			`where U: Into<T>;`
Print the conflicting impl on E0119 with external crate. 2017-10-22 10:14:53 -05:00
			`error: aborting due to 3 previous errors`

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