A modern programming language that makes developers happier.

kotlinlang

As per the suggestion cross-posting into <#C0B8Q383C|stdlib>

```result.recoverCatching { exception -&gt;
    throw SomeOtherException(exception)
}```

Isn't that slightly inefficient from a processing perspective as the JVM will need to generate the stacktrace etc?

the stacktrace is gathered when `SomeOtherException` is constructed, so you'll have that cost even without the `throw`.

(but yes, exceptional control flow is more expensive, just not for that reason)

if that matters, you can still use
```result.fold(onSuccess = { Result.success(it) }, onFailure = { Result.failure(transform(it)) })```
instead of your original

Thanks <@UJQB4DJF7> we've been using the `fold` method in our code, was just hoping for a slightly cleaner/more elegant solution