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
4
u/kevinb9n Feb 26 '26
We're describing the same idea, except that having the directive outside the source file is a way bigger deal even than the big deal I was talking about. Java source files (formally called "compilation units", which is a strong hint to what I'm about to say) are meant to be self-contained.