On Jun 2, 2015, at 2:01 PM, Mark S. Miller wrote: > Hi Scott, > > If the change is as simple as it appears, it seems it will go into ES6 itself!
The fix has already been made to the production copy that will be released in a couple weeks when we have ECMA GA approval Allen > > Thanks for pushing this forward. > > > On Tue, Jun 2, 2015 at 1:25 PM, C. Scott Ananian <ecmascr...@cscott.net> > wrote: > Thanks! It looks like core-js has already patched in the new spec: > https://github.com/zloirock/core-js/issues/75 > > I've opened https://github.com/paulmillr/es6-shim/issues/344 on es6-shim, and > I'll see if I can get a patch together for it. > > I've filed https://bugzilla.mozilla.org/show_bug.cgi?id=1170742 against > Mozilla. > I've filed https://code.google.com/p/v8/issues/detail?id=4161 against v8. > > Allen: Will this be an errata to ES6, part of ES7, or "something else"? > --scott > > > > > -- > Cheers, > --MarkM
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
