getOrThrow? about kotlin-result

[michaelbull]

Thanks for your suggestions.

orElseThrow should fit your use case (you can mapErr the failure state to a Throwable, then call orElseThrow).

Your trying is mostly the same as runCatching. Not a huge fan of the isInstance check going on in the catch statement though.

[Nimelrian]

Just saw that orElseThrow got added a few months ago. We've previously built a custom getOrThrow as well

fun <T> Result<T, Exception>.getOrThrow(): T =
    this.mapBoth({ it }, { throw it })

The most important distinction from orElseThrow is the user being able to instantly use the Ok value, without another call to unwrap (or the raw use of the value property of the Ok type) being needed. As @efenderbosch mentioned, the use case for this is a boundary to e.g. a framework, in our case Spring @Scheduled functions.

It would certainly be nice to have first party support in the library for this.

[efenderbosch]

Yeah, neither am I. Any suggestions on how to fix that?

[michaelbull]

Seems like it's in the stdlib Result, so probably worth adding. Will accept a PR, or get around to it in the new year otherwise.