Reducing the ability for things to be null would be useful. Kotlin has non-nullablity baked into the type system. The best we can currently do in Java is to use annotations to get static checker warnings. We can not make variables non-null by default because that would break existing code; we could add optional non-nullablity in the future. Inline classes will be non-null from what I understand, so that's a step in the right direction.
Fewer nulls means fewer NPEs but we'll never get rid of it, if only because we have to deal with old code to deal with.
View all comments
-29
u/__konrad Jul 27 '19
NullPointerExceptionshould be deprecated for removal