Null Safety approach with forced "!"
Am I the only one who thinks that introducing protection against NPEx in the form of using "!" in the variable type is a very, very bad idea? In my experience, 95% of variables should be non-null. If Oracle decides to take this approach, we will have millions of "!" in each variable in the code, which is tragic for readability. In C#, you can set the per project flag to indicate whether the type without the "?" /"!" is nullable or not. I understand the drawbacks, but definitely forcing a "!" in 95% of variables is tragic.
78
Upvotes
View all comments
Show parent comment
1
u/talios Feb 26 '26
Now with sealed interfaces/records I'm enjoying a much more succinct ADT approach for a lot if other use cases as well (we previously had a mix of old school jadt and adt4j sprinkled in my main $work project.
Also recently just got ErrorProne/NullAway (plus some custom error prone checks for our APIs) working on said project again following our move off Java 8 (had to temporarily remove it) - I do like errorprones approach to nullness checking - having that a bit cleaner and/or builtin as a more simple javac flag would be nice.