# Designing Errors with Kotlin

DevFeed: [Designing Errors with Kotlin](<https://devfeed.tech/articles/designing-errors-with-kotlin-29355.md>)

Original publisher: [Read original article](<https://arturdryomov.dev/posts/designing-errors-with-kotlin/>)

Author: Artur Dryomov

Published: 2018-12-18T00:00:00Z

Content type: tutorial

Language: en

Sources: [Artur Dryomov](<https://devfeed.tech/sources/artur-dryomov.md>)

Topics: [Kotlin](<https://devfeed.tech/topics/kotlin.md>), [Error Handling](<https://devfeed.tech/topics/error-handling.md>), [Exception](<https://devfeed.tech/topics/exception.md>), [Java](<https://devfeed.tech/topics/java.md>), [Swift](<https://devfeed.tech/topics/swift.md>)

Tags: [error-handling](<https://devfeed.tech/tags/error-handling.md>), [errors](<https://devfeed.tech/tags/errors.md>), [exception](<https://devfeed.tech/tags/exception.md>), [java](<https://devfeed.tech/tags/java.md>), [jvm](<https://devfeed.tech/tags/jvm.md>), [kotlin](<https://devfeed.tech/tags/kotlin.md>), [languages](<https://devfeed.tech/tags/languages.md>), [swift](<https://devfeed.tech/tags/swift.md>)

## AI overview

An article about designing error handling in Kotlin, using Java and Swift as points of comparison. It discusses checked and unchecked exceptions, documented return-value errors, and Swift's explicit error model.

## Source excerpt

Fun fact -- the area of the Java island is 138 793 km², the Kotlin island occupies 15 km². Of course, it is blatantly incorrect to compare languages based on same-named island areas. At the same time, it brings things in perspective. Java is the cornerstone of the JVM platform. The platform itself overshadows everything it hosts: Groovy, Ceylon, Scala, Clojure and Kotlin. It brings a lot to the table -- error handling is no exception (pun intended).