meanwhile you’d need to use something like `Either...

# arrow

[pakoito]

meanwhile you’d need to use something like EitherT<ForIO, MyError, A> which is slower and boilerplaty

[isto]

I'm already using EitherT in some other places, but that does not enable me to use MonadDefer instance's raiseError, does it? With EitherT I still have to manually handle either inside to computation

[isto]

My current understanding is that if I need errors that are not based on throwable out from my computation, I can achieve it with (https://github.com/istonikula/realworld-api/blob/feature/tagless-final/realworld-domain/src/main/kotlin/io/realworld/domain/articles/UseCases.kt#L154) or without EitherT (https://github.com/istonikula/realworld-api/blob/feature/tagless-final/realworld-domain/src/main/kotlin/io/realworld/domain/articles/UseCases.kt#L170)

[isto]

the added value of EitherT seems to be more flat computation which is easier to reason if there are many interdependent steps in my use case

[isto]

e.g. the latter linked FavoriteUseCase could be implemented using EitherT and I'd get rid of all the nesting

[simon.vergauwen]

I’m already using EitherT in some other places, but that does not enable me to use MonadDefer instance’s raiseError, does it?

[simon.vergauwen]

I just checked the EitherT effects instances I wrote couple weeks ago and they are fixed to Throwable atm.

[simon.vergauwen]

So we should create a ticket to make it take into account the left side of Either.