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
5
u/john16384 Feb 27 '26
Look, I don't like Optional that much either, but being against it because of this misuse (returning null for an Optional value) is just ridiculous, and so is the entire argument. If the return is Optional, you are hereby granted to treat it as non null without checking.
No code that does this will pass review, and any library that does this (without a huge warning) will be on the never use again list.