,
3 tweets,
1 min read
Read on Twitter
Current dilemma:
Directly use ZIO and its wonderful explicit error type,
or abstract over the effect type with a F[_] + cats-effect type-classes and lose the error in the type?
cc @jdegoes
Directly use ZIO and its wonderful explicit error type,
or abstract over the effect type with a F[_] + cats-effect type-classes and lose the error in the type?
cc @jdegoes
Having tried ZIO it's hard to go back, explicit error types (or their absence) make everything so clear and clean.
Only the fact of knowing that you already handled the errors, because you have a UIO[T], is priceless.
Only the fact of knowing that you already handled the errors, because you have a UIO[T], is priceless.
Also, I found that it's hard to abstract over the effect type in cats-effects if you have non-throwable errors.
That's mainly because Sync[F] extends MonadError[F, Throwable], so you are stick with Throwables if your F is a Sync.
That's mainly because Sync[F] extends MonadError[F, Throwable], so you are stick with Throwables if your F is a Sync.
