The one option that is mandated by an ISO standard.
Besides, if max and min are going to have a value without any parameter, it has to be exactly those Javascript uses. Unless you have a type that define other bounds for your numbers. And null always have a pointer type (that is object in Javascript), for the same reason that NaN always have a number type.
The one option that is mandated by an ISO standard.
Besides, if max and min are going to have a value without any parameter, it has to be exactly those Javascript uses. Unless you have a type that define other bounds for your numbers. And null always have a pointer type (that is object in Javascript), for the same reason that NaN always have a number type.
The only one that is bad on that list is D.
typeof null === "object"was actually a bug in the early implementations, and they decided to keep it in the spec: https://2ality.com/2013/10/typeof-null.html(see the comment from Brendan Eich)
Tony Hoare: “Introducing NULL was a billion-dollar mistake”
Brendan Eich: “Hold my undefined”
We had one
null, yes. But what about secondnull?Maybe D is too single quotes
0 == ''“This comparison appears to be unintentional”
D…Deez nutz!