2 ms·
I don’t know if it can be called a breaking change but it does feel like this is a pretty big deal. All your existing solutions are going to start throwing hund
by cm2187 9y ago
I don’t know if it can be called a breaking change but it does feel like this is a pretty big deal. All your existing solutions are going to start throwing hundreds of warnings.
In particular these future warnings should be all over everyone’s code:
1. Assigning or passing null to a non-nullable reference type: many functions have non optional arguments and for some actually expect null as an argument
6. Leaving a nonnullable field of a newly constructed object null after construction: there are many reasons why you may want to populate a field at a later stage, say you create two objects and you want them to cross reference each other’s.
It’s basically a fundamental change in the expected behaviour of reference types.