Nullable< HasValue或Nullable< T>之间有什么区别?！=空吗? [英] What is the difference between Nullable<T>.HasValue or Nullable<T> != null?

问题描述

我总是使用 Nullable<> .HasValue ，因为我喜欢这种语义.但是，最近我正在研究别人的现有代码库，他们在其中使用了 Nullable<>.！= null 专门代替.

I always used Nullable<>.HasValue because I liked the semantics. However, recently I was working on someone else's existing codebase where they used Nullable<> != null exclusively instead.

是否有理由优先使用一个，还是纯粹出于偏爱?

Is there a reason to use one over the other, or is it purely preference?

int? a;
if (a.HasValue)
    // ...

vs.

int? b;
if (b != null)
    // ...

推荐答案

编译器用对 HasValue 的调用替换了空比较，因此没有真正的区别.只要做对您和您的同事更具可读性/更有意义的事情即可.

The compiler replaces null comparisons with a call to HasValue, so there is no real difference. Just do whichever is more readable/makes more sense to you and your colleagues.

这篇关于Nullable< HasValue或Nullable< T>之间有什么区别?！=空吗?的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！