rust/src/test/ui/issues/issue-48728.stderr

error[E0119]: conflicting implementations of trait `std::clone::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 new impl of trait `std::clone::Clone` for type `[_]` in future versions

error: aborting due to previous error

For more information about this error, try `rustc --explain E0119`.
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-05 19:15:23 -05:00			error[E0119]: conflicting implementations of trait `std::clone::Clone` for type `Node<[_]>`:
Remove licenses 2018-12-25 09:56:47 -06: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-05 19:15:23 -05:00			`\|`
Update tests 2019-03-09 06:03:44 -06: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-05 19:15:23 -05:00			\| ^^^^^ conflicting implementation for `Node<[_]>`
			`...`
			`LL \| impl<T: Clone + ?Sized> Clone for Node<[T]> {`
			`\| ------------------------------------------- first implementation here`
Update existing tests for trivial bounds changes 2018-05-06 16:57:49 -05:00			`\|`
			= note: upstream crates may add new impl of trait `std::clone::Clone` for type `[_]` in future versions
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-05 19:15:23 -05:00
			`error: aborting due to previous error`

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