Or do I just read `result.value` directly?

# arrow

[Larry Garfield]

Or do I just read result.value directly?

[Wesley Hartford]

Yes, once you've ensured that its Right (or Left), you can access the value of either side simply using the value property.

[Larry Garfield]

OK. I was expecting an extraction syntax like in Rust. 🙂 But this works too.

[Wesley Hartford]

You can also avoid the when block and use functions like onLeft, onRight, getOrElse, etc.

[Larry Garfield]

Good to know. In this case I think the when is most logical, but won’t always be

[Alejandro Serrano.Mena]

in Kotlin we use mostly "smart casting", which means that once you go into a branch where you are sure that result has type Either.Right, it behaves as that type in every situation

[simon.vergauwen]

Ah too bad. Custom returns & implies contracts not supported in Kotlin 2.0. Otherwise this would've safely worked as well.

val x: Either<String, Int> = 1.right()
if (x.isRight()) {
    x.value
}