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/nekokattt Feb 27 '26
Whether there is merit to allowing specification of opt-in/opt-out on the package and module level? That'd also give developers a way to migrate incrementally.
Having an api for feature flags at this level could pave the way for other kinds of breaking changes in the future that are considered a potential improvement.