Observability of NaN distinctions — is this a concern?

David Bruant bruant.d at gmail.com
Wed Mar 20 12:33:55 PDT 2013

Le 20/03/2013 19:08, Jeff Walden a écrit :
> I don't see what can reasonably be done about it, without effectively mandating attempting NaN-substitution whenever the value to set might be NaN.
+1. I think Safari needs to be fixed.
Stuffing info in NaNs sounds superfluous. JS has objects, arrays, Typed 
Arrays, strings. Largely enough legitimate mechanisms to represent 
informations without having to add a hacky one. That would be sending a 
wrong signal to developers in my opinion.


More information about the es-discuss mailing list