You literally can open two KEEPs, one for Result type which is primary intended to represent result of continuations and one for high-level overview of Rich Errors and read why it's not what you're asking. Kotlin is not Scala and never trying to be one
This is others is just matter of your choice and bias. Java allows to write a lot of bad code too, that's why Effective Java book exists
1
u/javaprof Nov 06 '25
> to be a proper monad.
> proper Result monad.
You literally can open two KEEPs, one for Result type which is primary intended to represent result of continuations and one for high-level overview of Rich Errors and read why it's not what you're asking. Kotlin is not Scala and never trying to be one
This is others is just matter of your choice and bias. Java allows to write a lot of bad code too, that's why Effective Java book exists