A non type should be a type. It should be of the type none. And it is in good script languages like Python so I don't know why you think it shouldn't.

[–] Remavas@programming.dev 1 points 4 days ago (1 children)

They say a picture is worth a thousand words.

collapsed inline media

[–] Valmond@lemmy.world 1 points 3 days ago (1 children)

That's a Numpy type, not a Python typesm, try a=None b=None a==b

[–] Remavas@programming.dev 1 points 2 days ago* (last edited 2 days ago)

That's not a type. A NaN is a floating point number (of type float). I used numpy because that's the easiest way to get a NaN.

This is part of the floating point standard.

This was never about None, which is a completely different thing.

[–] powermaker450@discuss.tchncs.de 4 points 1 week ago (1 children)

probably not true in most other langauges. although I'm not well versed in the way numbers are represented in code and what makes a number "NaN", something tells me the technical implications of that would be quite bad in a production environment.

the definitive way to check for NaN in JS would probably be something like

// with `num` being an unknown value

// Convert value to a number
const res = Number(num);

/*
 * First check if the number is 0, since 0 is a falsy
 * value in JS, and if it isn't, `NaN` is the only other
 * falsy number value
 */
const isNaN = res !== 0 && !res;

[–] Remavas@programming.dev 2 points 4 days ago

NaN is a special floating point value. https://en.wikipedia.org/wiki/IEEE_754

It's weird but it makes sense why it was chosen to be this way.