Skip to content
This repository has been archived by the owner on Feb 27, 2021. It is now read-only.

Equal[Option[A]] ambiguity with Cats 2.2.0 #116

Open
nigredo-tori opened this issue Nov 10, 2020 · 1 comment
Open

Equal[Option[A]] ambiguity with Cats 2.2.0 #116

nigredo-tori opened this issue Nov 10, 2020 · 1 comment

Comments

@nigredo-tori
Copy link

nigredo-tori commented Nov 10, 2020

Scastie. With Shims 2.2.0 and Cats 2.2.0, we get this:

import scalaz.Scalaz._
import shims.eqToScalaz

implicitly[scalaz.Equal[Option[Short]]]
//ambiguous implicit values:
// both method optionOrder in trait OptionInstances of type [A](implicit A0: scalaz.Order[A])scalaz.Order[Option[A]]
// and method eqToScalaz in trait EqConversions of type [A](implicit AC: shims.util.Capture[cats.kernel.Eq[A]])scalaz.Equal[A] with shims.conversions.Synthetic
// match expected type scalaz.Equal[Option[Short]]
//could not find implicit value for parameter e: scalaz.Equal[Option[Short]]
//not enough arguments for method implicitly: (implicit e: scalaz.Equal[Option[Short]])scalaz.Equal[Option[Short]].
//Unspecified value parameter e.
@nigredo-tori
Copy link
Author

nigredo-tori commented Nov 10, 2020

Looks like there are a lot of other compatibility issues with Cats 2.2.0 - see the test failure in the scala-steward PR.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant