rust/tests/ui/issues/issue-48728.stderr

error[E0119]: conflicting implementations of trait `Clone` for type `Node<[_]>`
  --> $DIR/issue-48728.rs:4:10
   |
LL | #[derive(Clone)]
   |          ^^^^^ conflicting implementation for `Node<[_]>`
...
LL | impl<T: Clone + ?Sized> Clone for Node<[T]> {
   | ------------------------------------------- first implementation here
   |
   = note: upstream crates may add a new impl of trait `std::clone::Clone` for type `[_]` in future versions
   = note: this error originates in the derive macro `Clone` (in Nightly builds, run with -Z macro-backtrace for more info)

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 `Clone` for type `Node<[_]>`
Remove licenses 2018-12-25 15:56:47 +00:00			`--> $DIR/issue-48728.rs:4:10`
do not propagate `Err` when determing causal info In intercrate mode, if we determine that a particular `T: Trait` is unknowable, we sometimes also go and get extra causal information. An errant `?` was causing us to propagate an error found in that process out as if `T: Trait` was not unknowable but rather not provable. This led to an ICE. 2018-04-06 00:15:23 +00:00			`\|`
Update tests 2019-03-09 12:03:44 +00:00			`LL \| #[derive(Clone)]`
do not propagate `Err` when determing causal info In intercrate mode, if we determine that a particular `T: Trait` is unknowable, we sometimes also go and get extra causal information. An errant `?` was causing us to propagate an error found in that process out as if `T: Trait` was not unknowable but rather not provable. This led to an ICE. 2018-04-06 00:15:23 +00:00			\| ^^^^^ conflicting implementation for `Node<[_]>`
			`...`
			`LL \| impl<T: Clone + ?Sized> Clone for Node<[T]> {`
			`\| ------------------------------------------- first implementation here`
Revert "Rollup merge of #62696 - chocol4te:fix_#62194, r=estebank" This reverts commit df21a6f040a7011d509769a61ac7af9502636b33, reversing changes made to cc16d0486933e02237190366de2eb43df2215c11. 2019-08-04 16:52:43 +00:00			`\|`
Fix a minor grammar nit, update UI tests 2019-09-18 22:16:16 +00:00			= note: upstream crates may add a new impl of trait `std::clone::Clone` for type `[_]` in future versions
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)
do not propagate `Err` when determing causal info In intercrate mode, if we determine that a particular `T: Trait` is unknowable, we sometimes also go and get extra causal information. An errant `?` was causing us to propagate an error found in that process out as if `T: Trait` was not unknowable but rather not provable. This led to an ICE. 2018-04-06 00:15:23 +00:00
			`error: aborting due to previous error`

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