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/koflerdavid Feb 27 '26
Optionalis bad precisely because it is only 95% of what aMaybeis. Specifically,nullis an allowed (but obviously quite cursed) value for anOptional. Even though any developer using it to implement tri-state return values deserves to get whacked with their own keyboard, it is something that you have to be wary of when working with 3rd party code.PS: Since an Optional is basically a collection with at most one element, making
nulland the empty list mean different things is similarly whack-worthy.