我总是使用 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)
// ...
对比
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<T>.HasValue 或 Nullable<T> 之间有什么区别?!= 空?的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持跟版网!