Nullable type semantics

[waxen musk]

is

value.HasValue

always the same as

value != null

or

value is not null

Context: using System.Nullable<T>

Nullable type semantics

[spice patio]

You can check this yourself: https://lab.razor.fyi/#4-pl5OIKKMpPL0rM1UsuFqq35uJKys_PUXDLM9TIzCuxVyhLzClN1VSwtYOw9DwSi8NADIRCI6wKFRRtFfJKc3IQ6oyxq8ssVsjLL4Gq9WJKLo7i5Piw-_S536kCLAmMAA

Look at the compiled C#, all of them are the same.

[rancid cliff]

wouldn't they be different (specifically !=) for UnityEngine.Object

[cinder hollow]

These checks are being done on Nullable<T>, not on the T itself so it shouldn't matter

[rancid cliff]

🤔 is Nullable<T> the same as T??

[spice patio]

Confusingly, no.

TStruct? is a syntax sugar for Nullable<TStruct>, which is a wrapper type that actually exists at runtime.
TClass? is just TClass but with NRT, which is just a compile time feature that doesn't exist at runtime.

This nullable divide brings not only confusion but also extra baggage when dealing with generics, think T? Get<T>().

[ruby shadow]

Yeah, I don't see a point in using nullables for reference types. It can be useful for structs, but too confusing otherwise.

[waxen musk]

danke