A modern programming language that makes developers happier.

kotlinlang

&gt; For example, there are no implicit widening conversions for numbers ...

Why not?

<https://kotlinlang.org/docs/reference/basic-types.html>

<https://kotlinlang.org/docs/reference/basic-types.html#explicit-conversions>

chuck: Because their behavior is frequently unexpected, and as a rule Kotlin doesn’t perform implicit conversions between types.

<http://www.javapuzzlers.com/java-puzzlers-sampler.pdf> puzzle 1 has an example of a widening conversion creating “unexpected” behavior.

I kinda miss this too. I guess I would forgive some unexpected behvavior in few edge cases for not having to write `toInt()` or `toDouble()` fifty times in one file when working with any sort of math or graphics library.

I agree it can be annoying, although I find that being able to define `val Byte.i: Int get() = this.toInt() and 0xFF` does a pretty good job of compensating for the shortcoming (when working with Bytes, for example).