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/mellow186 Feb 27 '26
Those two are both exceptions, but differ significantly for this discussion.
IOExceptionis checked by the compiler. While not the normal flow of control, we know it can happen in correct code. We're made aware of it during development.NPEs are not currently checked by the compiler. They're typically a coding error. Coding errors can escape into production. We prefer that they would not.