Kotlin’s type system will catch that kind of error...
# getting-started
s
Kotlin’s type system will catch that kind of error most of the time because you [mostly] have to be explicit about what you accept and return when writing a function, but it’s a weak guarantee