Do we really need Effect type, instead of () => Promise<Either>?
I believe it's possible to replace all uses of
It's not hard to implement
I can see lack of the capability to write sync and async code in the same manner, but I don't consider it as a disadvantage.
Also
There is a point, that
In my opinion all cons are minor. But switching to
So my question is "do we really need Effect type, instead of () => Promise<Either>"?
Effect<A, E, R>(r: R) => Promise<Either<E, A>>RRecordIt's not hard to implement
provideI can see lack of the capability to write sync and async code in the same manner, but I don't consider it as a disadvantage.
Also
Effect.genyield*There is a point, that
EffectIn my opinion all cons are minor. But switching to
() => Promise<Either>So my question is "do we really need Effect type, instead of () => Promise<Either>"?
Similar Threads
Was this page helpful?
