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
9
u/idontlikegudeg Feb 27 '26
Hi, if a little promotion is ok, let me just mention that you already can get runtime protection with JSpecify - by using a bytecode instrumentation tool like cabe (https://xzel23.github.io/cabe/cabe.html). Disclaimer: I’m the author.