Standard builtins' prototypes and toString

Till Schneidereit till at
Tue Jun 17 13:41:31 PDT 2014

On Tue, Jun 17, 2014 at 6:07 PM, Mark Miller <erights at> wrote:

> I am happy with #b as well, though I prefer #c. I also agree with C.
> Scott's interpretation of #c, to mean, appropriate degenerate value, which
> is generally the zero value, but is plausibly NaN for Date.
> Whichever experiment Nightly tries first with a positive outcome, I expect
> that's what we'll do, since the difference between #b and #c is not large
> enough to be worth waiting for a second experiment.

I don't much care which one we choose, to be honest. I kinda doubt that #b
will have more compatibility issues than #c[1], and find conceptually
cleaner by a thin margin: a non-Date object isn't an invalid Date, it's not
a Date. But then again, if you don't want an object to be treated as a
Date, don't call Date's toString on it? Implementation-wise, it's pretty
much a wash, at least.

[1]: and for all I know there might be content out there that relies on an
exception being thrown if Date#toString is used on a non-Date object ...
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the es-discuss mailing list