I think this, and the fact that NaN == NaN is false, make perfect sense.
NaN is the result of mathematically undefined behavior. You’re not going to get a NaN outside of a number context, so tying it together in the Number scope is fine.
Yep. There are some languages where this applies, because it’s a mathematical concept. The point is it’s the same ‘no value’ concept, which isn’t shared byimplemented the same way by all languages.
C is strongly typed, and uses pointers, so NULL sort of intrinsically has a value in C.
Comments
I think this, and the fact that NaN == NaN is false, make perfect sense.
NaN is the result of mathematically undefined behavior. You’re not going to get a NaN outside of a number context, so tying it together in the Number scope is fine.
Same reason NULL != NULL. It makes sense if you understand how these values work.
That doesn’t smell right.
https://richiban.uk/2016/12/21/does-null-equal-null/
ISNULL may be true, whilst NULL != NULL. NULL is not a value.
Ah, my brain was in C mode, where NULL is functionally 0. This is about the concept, which doesn’t apply equally to all languages.
Yep. There are some languages where this applies, because it’s a mathematical concept. The point is it’s the same ‘no value’ concept, which isn’t
shared byimplemented the same way by all languages.C is strongly typed, and uses pointers, so NULL sort of intrinsically has a value in C.
edit: my wording was a bit off
You can kinda think of it as null meaning undefined. In this case, “undefined does not equal undefined” seems easier for me to wrap my head around
[deleted]
Sign in to comment. Sign in