We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I found myself needing to tap the full Exit<A, E> of an Effect instead of using tapErrorCause and tap separately. I think it would be a useful helper.
Exit<A, E>
Effect
tapErrorCause
tap
export const tapExit = dual< <A, E, X, E2, R2>( f: (exit: Exit.Exit<A, Types.NoInfer<E>>) => Effect.Effect<X, E2, R2> ) => <R>(self: Effect.Effect<A, E, R>) => Effect.Effect<A, E | E2, R | R2>, <A, E, R, X, E2, R2>( self: Effect.Effect<A, E, R>, f: (exit: Exit.Exit<A, E>) => Effect.Effect<X, E2, R2> ) => Effect.Effect<A, E | E2, R | R2> >(2, (self, f) => Effect.matchCauseEffect(self, { onFailure: (cause) => Effect.zipRight(f(Exit.failCause(cause)), Effect.failCause(cause)), onSuccess: (value) => Effect.zipRight(f(Exit.succeed(value)), Effect.succeed(value)), }))
No response
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the problem this feature would solve?
I found myself needing to tap the full
Exit<A, E>
of anEffect
instead of usingtapErrorCause
andtap
separately. I think it would be a useful helper.What is the feature you are proposing to solve the problem?
What alternatives have you considered?
No response
The text was updated successfully, but these errors were encountered: