I always advocated for this kind of change in C# and now I&#x27;m using Swift I&#x27;m definitely sure that non-nullability should be available in any kind of OO-language. There aren&#x27;t that many use cases that require nullability of a reference and there are many cases where the forced nullability bites you.<p>Unfortunately adding it to C# now will mean that either the language breaks or the feature will be an add-on that isn&#x27;t as powerful as it should be (like in Swift, where it&#x27;s really the base for everything).<p>Personally I would say that a reference type can be declared explicitly non-nullable with an exclamation mark (!) and if they&#x27;re properties they either should have a default value or they should be set while the class is constructed.