3 ms·
Yeah, the second not being an compile error allows for legacy code to call functions with notnull arguments but I do not think that is necessarily a good thing.
by jeltz 2y ago
Yeah, the second not being an compile error allows for legacy code to call functions with notnull arguments but I do not think that is necessarily a good thing. Hard to say without using it in practice though.
- vbezhenar 2y agoCompiler will insert null checks in the function invocation. It's not a problem. And if you can't gradually migrate old code to null types, it means that most projects will never utilize those types.
- jeltz 2y agoYeah, the more I think about it the more O agree with the design even if it surprised me at first.