Trying #c on Nightly would provide us the information needed to bring #c to consensus.
On Tue, Jun 17, 2014 at 2:10 AM, Till Schneidereit < [email protected]> wrote: > On Thu, Jun 12, 2014 at 10:42 PM, C. Scott Ananian <[email protected]> > wrote: > >> On Thu, Jun 12, 2014 at 3:56 PM, Mark S. Miller <[email protected]> >> wrote: >> > I like this list. I prefer #c. >> > * We have previously succeeded at making previously non-generic methods >> > generic. I think we could get away with #c. >> > * It is easier for a normal JS programmer to do the equivalent of #c for >> > most of their classes. >> >> FWIW, if a change to the spec is needed, I also favor (c). >> >> Both generic options (b) and (c) have consistent behavior that can >> extend to `#valueOf`. In option (b) you would presumably invoke >> `Object#valueOf` and for option (c) you'd return the "zero" value. >> > > Is this close-ish to a consensus? If so, we'd implement and land it on > Nightly to get an idea of its web compatibility. It doesn't sound like > there's a meaningful danger of implementing something seriously > incompatible with what the spec is going to say - if (c) is roughly adopted. > -- Cheers, --MarkM
_______________________________________________ es-discuss mailing list [email protected] https://mail.mozilla.org/listinfo/es-discuss
