Zio interoperability #71
Conversation
It order to empowered more taggeless final users and simplify migrations from/to ZIO we introduce some interoperability library for it. This library works the same way that Monix interoperability. It's currently working only on JVM, ScalaJS support will follow (for now it won't compile). Be aware that if you are completely commit to either Monix or ZIO both libraries already have their internal support for retry policies.
| .settings( | ||
| resolvers += Resolver.sonatypeRepo("releases"), | ||
| libraryDependencies ++= Seq( | ||
| "dev.zio" %%% "zio" % "1.0.0-RC11-1", |
There was a problem hiding this comment.
How long do you think it will be before we see ZIO 1.0.0? Is it worth waiting for that? As I understand it, cats-effect 2.0.0 and Monix 3.0.0 should be out very soon, so it would be nice to do a release with all the dependencies on stable versions.
There was a problem hiding this comment.
I don't know when it will be release but I think it will be soon. I agree we should wait stable versions to make releases.
|
Thanks! This looks good. As you say, ZIO already has features similar to cats-retry available out of the box, so I'm not sure how useful this integration is, but there's no harm in providing it as an option for people to use. I'm curious about why the ScalaJS support doesn't compile? |
|
ScalaJS doesn't work because of missing Cats Applicative typeclass instance for ZIO. I asked on the Gitter channel they are apparently working on it. |
It order to empowered more taggeless final users and simplify migrations
from/to ZIO we introduce some interoperability library for it. This
library works the same way that Monix interoperability. It's currently
working only on JVM, ScalaJS support will follow (for now it won't compile).
Be aware that if you are completely commit to either Monix or ZIO both
libraries already have their internal support for retry policies.