Using Nullable vs int? from a compilation performance point-of-view in Visual Studio

Asked Feb 16 '17 at 20:06

Active Feb 16 '17 at 20:06

Viewed 50 times

I understand, from looking through previous questions on the topic, that Nullable<int> and int? get compiled to the same CIL. But it was pointed out that since Nullable needed the using System directive, it would make compilation as well as Intellisense slower if using int? made the using System directive unnecessary.

So my question is this:

Does the compiler (using C# 6.0 on .NET 4.6.1 on Visual Studio Professional 2015) work harder to produce CIL code when it interprets Nullable<int> vs int? ?

asked Feb 16 '17 at 20:06

adyavanapalli

4

I think that'll be roughly proportional to the difference between `int` and `Int32`. – 15ee8f99-57ff-4f92-890c-b56153 Feb 16 '17 at 20:08
@Ed Is there any way to quantify your answer? – adyavanapalli Feb 16 '17 at 20:09
2

Sorry, I was trying to be funny. They're synonymous. – 15ee8f99-57ff-4f92-890c-b56153 Feb 16 '17 at 20:10
Why do you think compilation and intellisense are slower when the `using System;` directive is present? – D Stanley Feb 16 '17 at 20:24
@D Stanley See Pop Catalin's answer in http://stackoverflow.com/questions/136278/why-should-you-remove-unnecessary-c-sharp-using-directives?noredirect=1&lq=1 – adyavanapalli Feb 16 '17 at 20:28

Using Nullable vs int? from a compilation performance point-of-view in Visual Studio

0 Answers0