I always thought that NaN is required by IEEE rules to never equal any other number, including itself, because you can make NaN in different ways and this shouldn’t result in equality or something, so C is wild but not javascript’s fault.
The other three being true is definitely javascript’s insane fault, though.
yep, because it’s two different instances of an object
I always thought that NaN is required by IEEE rules to never equal any other number, including itself, because you can make NaN in different ways and this shouldn’t result in equality or something, so C is wild but not javascript’s fault.
The other three being true is definitely javascript’s insane fault, though.