"Not a number" is a number :/

JS 🤦‍♂️

@karma "Jabba the Script" ¯\_(ツ)_/¯

I agree on JS being one of the most counter-intuitive programming languages but this one actually makes sense. If you expect your method to return a value type of number then youre screwed if you get something else. That's why they made NaN of type number so it can be returned by functions that are supposed to return numbers. The caller then just has to check if the value is NaN.

@exelix I know.
Also, there was a set of puzzles, where I had solved things like these X!=X and
A ==B, B==C, A!=C.

The society we live in...

To check if something is an apple, you need an apple type thing

It's probably equal to 0

@venky too bad simple stuff like that passes over the head of so-called "developers"

@exelix https://developer.mozilla.org/en-US... Problem solved

isNaN(parseFloat(‘😹🦞🦆’)) === true this is always true!

Came here to say the same thing as @exelix did.

Quote: "For example, a bit-wise IEEE floating-point standard single precision (32-bit) NaN would be: s111 1111 1xxx xxxx xxxx xxxx xxxx xxxx where s is the sign (most often ignored in applications) and the x sequence represents a non-zero number (the value zero encodes infinities). The first bit from x is used to determine the type of NaN: "quiet NaN" or "signaling NaN". The remaining bits encode a payload (most often ignored in applications)"

There are some special values in floating point numbers as defined by IEEE-754 there are for example two numers for 0, one when aproaching from + infinite and one for aproaching from - infinite (set by the sign bit) in oposition to the normal two complement integers. There's also a special number for division by zero and for stuff like NaN (ex. Division by +/- infinite and such stuff). So yes technically they are numbers. Just instead of encoding numbers they are agreed upon to encode special/edge cases.

Nani? My brain just crashed seeing this..