should it be raiseException or raiseError? cc <@U0...

# arrow

[pakoito]

should it be raiseException or raiseError? cc @aballano and @simon.vergauwen for opinion

[Hiosdra]

For that, I meant version with raiseError. I have seen that there is already with raiseException 😉

[pakoito]

ye I imagined 😄

[aballano]

I guess Simon knows better, but from my understanding it should be raiseError without the mapping 🤔

[pakoito]

toIO and toIOException to distiguish IO<Throwable, A> and IO<Nothing, A> for example

[pakoito]

@Hiosdra you could make a PR for that

[Hiosdra]

@pakoito Thank you, I will be glad to do this today evening.
You mean to rename actual:

fun <A> Either<Throwable, A>.toIO(): IO<Nothing, A>

to toIOException
Also to create and test:

fun <E, A> Either<E, A>.toIO(): IO<E, A> =
  fold({ IO.raiseError(it) }, { IO.just(it) })

[pakoito]

correct!

[pakoito]

so there should be 3 in the end:

[pakoito]

oh nevermind, just 2

[pakoito]

the third one can be made by using map or mapLeft first

[Hiosdra]

Ok, I will make pull request after my work 😉

[pakoito]

fun <E, A> Either<Throwable, A>.toIO(f: (Throwable) -> E): IO<E, A>

[pakoito]

cool, thanks 😄

[Hiosdra]

@pakoito https://github.com/arrow-kt/arrow/pull/2003
Can you look at it?