Why no one recommends the use of the standard library's Result class but a custom sealed class approach?

• kotlin-result

  35 936 8.8 Kotlin

  A multiplatform Result monad for modelling success or failure operations.

Many people were not satisfied with basic sealed classes or Kotlin's Result class, and opted to either write their own implementation, use an existing one (like https://github.com/michaelbull/kotlin-result), or use Arrow.

• resukt

  2 2 0.0 Kotlin

  A Result type representing either a success or a failure.

I made a result library, but unlike the sealed class approach, the implementation is basically copy-pasted from stdlib, except it is Result and a few changes. https://github.com/Jason5Lee/resukt

• WorkOS

  workos.com sponsored

  The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.

  

• kotlinx.coroutines

  59 12,710 8.9 Kotlin

  Library support for Kotlin coroutines

  

Sure! runCatching catches Throwable right? Well when you cancel a coroutine it throws a CancellationException and this gets used as a signal to stop execution. runCatching stops that signal so the coroutine keeps running. Lemme find you a link real quick https://github.com/Kotlin/kotlinx.coroutines/issues/1814

• KEEP

  61 3,279 5.5 Markdown

  Kotlin Evolution and Enhancement Process

  

Suggest a related project