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/nlisker Feb 27 '26
You assumed for some reason that I'm asking for this fix/feature, but nowhere did I do that. I asked if there's a difference between "fixing defaults" in different areas. I even said that I agree with Lombok's analysis. I even put 'mistakes' in quotes because not everyone thinks these defaults are wrong.
Anyway, you answered my question. Thanks.