Initializer expression on for-in syntax subject
Mark S. Miller
erights at google.com
Fri Mar 14 13:29:23 PDT 2014
On Fri, Mar 14, 2014 at 12:29 PM, David Herman <dherman at mozilla.com> wrote:
> Sad panda. At least we can disable it in strict mode, right?
>
yes!
>
> And who knows, maybe some day, some day...
>
> Dave, dreaming of ES24
>
I'll hazard a public prediction for the record:
Since ES6 does implicit strict opt-in for both classes and modules, by the
time of wide ES7 deployment, sloppy mode will no longer matter much for new
code. Or ES8 at the latest.
It's just a prediction, so no need to argue until we're in the predicted
timeframe.
> On Mar 13, 2014, at 4:59 PM, Oliver Hunt <oliver at apple.com> wrote:
>
> > JSC has been trying to kill off the initialiser expression in the
> for(in) statement, but we've encountered a bunch of reasonably significant
> content that breaks with it disallowed (a particularly prominent one
> currently is http://battlelog.battlefield.com/bf4/), so we will be
> bringing back support for
> >
> > for (var Identifier = Expression in Expression)
> >
> > --Oliver
> > _______________________________________________
> > es-discuss mailing list
> > es-discuss at mozilla.org
> > https://mail.mozilla.org/listinfo/es-discuss
>
> _______________________________________________
> es-discuss mailing list
> es-discuss at mozilla.org
> https://mail.mozilla.org/listinfo/es-discuss
>
--
Cheers,
--MarkM
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.mozilla.org/pipermail/es-discuss/attachments/20140314/e157d3f3/attachment.html>
More information about the es-discuss
mailing list