A few things you might not know about System.Nullable
There is plenty of information about
Nullable<T> type out there and how to use it. There are, however a few tidbits that are not quite as obvious at first glance.
It’s a struct that can be null. The only reason why
int? intVal = null; compiles is because C# compiler supports nullable types. You cannot define the same kind of struct yourself.
The decision to make
Nullable<T> a value type actually makes sense if you think about it. Calling its member methods and properties will always succeed, i.e. NullReferenceException will never be thrown. This gurantees that
HasValue never throws a NullReferenceException.
#Comparison to null
Under the hood, the compiler, in fact translates comparison to null to a call to HasValue. The below MSIL demonstrates that:
As you can see the generated IL for
hasvalue = value.HasValue and
hasvalue2 = value != null are identical.
Also from above code you can see that assigning null to a nullable value is the same as calling the parameterless contructor (which all value types have).
C# compiler also does special things with ternary operator for nullable types. The following code compiles:
The above is just syntactic sugar for calling
HasValue and if it’s true calling GetValueOrDefault(). The compiler actually generates a temporary variable to call
HasValue off in both Release and Debug modes. Not sure why that is. Below code illustrates the equivalent C# code to what the compiler generates for ternary operator.
Nullable<T> is a special value type that has support from C# compiler to allow the following:
nullassignment - under the hood: calling defualt constructor.
nullcomparison - under the hood: calling
- ternary operator
??- under the hood: calling
blog comments powered by Disqus