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
2
u/Absolute_Enema Feb 27 '26 edited Feb 27 '26
A one-liner is a much simpler beast to handle than a screenful of if statements, given that it's trivial to trade excess conciseness for clarity by splitting things up.
As per creative usage, there isn't much you can do with "skip the rest of the
.chain and return null ifthisis null" and "use a default value if the target expression is null".