You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Importing cats.instances.future._ is still required to summon typeclass instances for scala.concurrent.Future, e.g.
importcats.Applicativeimportscala.concurrent.Futureimportscala.concurrent.ExecutionContext.Implicits.globalApplicative[Future]
// Could not find an instance of Applicative for scala.concurrent.Futureimportcats.instances.future._Applicative[Future]
// cats.Applicative[concurrent.Future] = cats.instances.FutureInstances$$anon$1@479111ba
This was the only cats.instances import I needed to keep around when upgrading a large codebase that strictly uses a la carte imports from v2.1.1 to v2.2.0-RC2.
The text was updated successfully, but these errors were encountered:
I believe there was some discussion about this somewhere, and that excluding them was a design decision, but I don't remember the details, and I'm not committed to either including or excluding them from implicit scope.
This #2334 may or may not be what @travisbrown is referring to, but I'm adding it here for reference as that discussion is still open and marked for milestone 3.0
Importing
cats.instances.future._
is still required to summon typeclass instances forscala.concurrent.Future
, e.g.This was the only
cats.instances
import I needed to keep around when upgrading a large codebase that strictly uses a la carte imports from v2.1.1 to v2.2.0-RC2.The text was updated successfully, but these errors were encountered: