Heya all! I’ve written an article around various e...

# feed

[mitch]

Heya all! I’ve written an article around various error handling strategies in Kotlin, in particular on how they compare to one another in terms of succinctness, readability, and overall cognitive complexity score. In this article I’ve also compared Arrow’s current typed-error handling approach, as well as one with context receivers presented at KotlinConf ’23 which seemingly also gaining some traction.

This is a survey study from various programming trends in several developer cohorts in my friends/colleagues circle so it may or may not apply internationally. If you have an approach that you’d like to share, please drop them in the comment. As well if you noticed anything that wasn’t accurate or something that needs better clarification, please let me know in the comment! If you like the article please don’t forget to also share this to your colleagues, leave a comment perhaps several claps.

https://medium.com/@mitchellyuwono/typed-error-handling-in-kotlin-11ff25882880

[Norbi]

Arrow’s context(Raise<E>) achieved the most optimized score on all aspects of developer productivity

I agree... so let's hope that context receivers will be available for Kotlin multiplatform soon.

[Erik Dreyer]

Great article. I’ve been experimenting with your example of using context receivers / arrow to bake in the error handling with really nice and clean results. Talk about a power feature!