> NaN == NaNfalse> NaN === NaNfalse> NaN !== NaNtrue>
Counterintuitively, it would seem that NaN does not equal NaN. But let's think about this for a second. Is it really that strange or just a symptom of what the logical symbol NaN actually stands for?
Thing is, NaN stands for "Not a Number" and if memory serves comes right out of IEEE754 floating point arithmetic. It's very handy for representing things like 0/0, different kinds of infinity and operations involving infinities. In short, it represents an undefinable number.
Now, what could possibly be the result of comparing two undefinable numbers?
Can anyone tell me if other languages handle this differently? Just produce an error of some sort?
Here's how it works 👇
Then get thoughtful letters 💌 on mindsets, tactics, and technical skills for your career.
"Man, love your simple writing! Yours is the only email I open from marketers and only blog that I give a fuck to read & scroll till the end. And wow always take away lessons with me. Inspiring! And very relatable. 👌"
Ready to Stop copy pasting D3 examples and create data visualizations of your own? Learn how to build scalable dataviz components your whole team can understand with React for Data Visualization
Curious about Serverless and the modern backend? Check out Serverless Handbook, modern backend for the frontend engineer.
Ready to learn how it all fits together and build a modern webapp from scratch? Learn how to launch a webapp and make your first 💰 on the side with ServerlessReact.Dev
By the way, just in case no one has told you it yet today: I love and appreciate you for who you are ❤️