The whole java-interop with null-pointers in Kotli...
# announcements
s
The whole java-interop with null-pointers in Kotlin is actually not really useful in practice. Programmers are easily getting used to the null-safety within Kotlin and do not always check for the type with exclamation-marks X! . Also, casting from X! to X? is marked as "useless" by the compiler (which it is not, because X? is treated differently by the compiler than X!). Why are not all types coming from Java automatically null-unsafe X? instead of X! ?? Sometimes the null-safe types X? seem like a Option<X> with a little bit of syntax sugar in the form of ?. ?: and such.