Unship ES2015 for-in initializer restrictions

Unship ES2015 for-in initializer restrictions

We now have data that 0.011% of websites use the pattern
  for (var i = 0 in j) { ... }
This pattern was banned by ES2015, with the idea to revisit if
it presents a web compatibility problem. Informally, after
the May 2016 TC39 meeting, the new data was discussed, and there
was interest in reversing the decision. Although the specification
is not yet updated, it seems likely to come soon.

This patch turns off the flag which bans that construct, reenabling
it. The change should prevent websites from breaking.

BUG=v8:4942
Committed: https://crrev.com/7245dabdb1c4f7dc5fec06cc087e9c4180df474a
Cr-Commit-Position: refs/heads/master@{#36562}

[Dan Ehrenberg, 2016-05-27 09:40:54]

The CQ bit was checked by littledan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-05-27 09:41:01]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2011223003/1
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2011223003/1

[Dan Ehrenberg, 2016-05-27 09:41:22]

littledan@chromium.org changed reviewers:
+ adamk@chromium.org, rossberg@chromium.org

[Dan Ehrenberg, 2016-05-27 09:54:56]

On 2016/05/27 at 09:41:23, Dan Ehrenberg wrote:
> 

If this goes in, we should backport it to 52 as well.

[commit-bot: I haz the power, 2016-05-27 09:57:30]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-05-27 09:57:31]

Dry run: Try jobs failed on following builders:
  v8_linux_nodcheck_rel_ng on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_nodcheck_rel_ng/bu...)
  v8_linux_nodcheck_rel_ng_triggered on tryserver.v8 (JOB_FAILED,
http://build.chromium.org/p/tryserver.v8/builders/v8_linux_nodcheck_rel_ng_tr...)

[Dan Ehrenberg, 2016-05-27 13:21:17]

The CQ bit was checked by littledan@chromium.org to run a CQ dry run

[commit-bot: I haz the power, 2016-05-27 13:21:19]

Dry run: CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2011223003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2011223003/20001

[commit-bot: I haz the power, 2016-05-27 14:21:01]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2016-05-27 14:21:02]

Dry run: This issue passed the CQ dry run.

[adamk, 2016-05-27 18:56:24]

lgtm

[Dan Ehrenberg, 2016-05-27 19:10:18]

The CQ bit was checked by littledan@chromium.org

[commit-bot: I haz the power, 2016-05-27 19:10:28]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/2011223003/20001
View timeline at
 https://chromium-cq-status.appspot.com/patch-timeline/2011223003/20001

[commit-bot: I haz the power, 2016-05-27 19:12:10]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-05-27 19:14:53]

Description was changed from

==========
Unship ES2015 for-in initializer restrictions

We now have data that 0.011% of websites use the pattern
  for (var i = 0 in j) { ... }
This pattern was banned by ES2015, with the idea to revisit if
it presents a web compatibility problem. Informally, after
the May 2016 TC39 meeting, the new data was discussed, and there
was interest in reversing the decision. Although the specification
is not yet updated, it seems likely to come soon.

This patch turns off the flag which bans that construct, reenabling
it. The change should prevent websites from breaking.

BUG=v8:4942
==========

to

==========
Unship ES2015 for-in initializer restrictions

We now have data that 0.011% of websites use the pattern
  for (var i = 0 in j) { ... }
This pattern was banned by ES2015, with the idea to revisit if
it presents a web compatibility problem. Informally, after
the May 2016 TC39 meeting, the new data was discussed, and there
was interest in reversing the decision. Although the specification
is not yet updated, it seems likely to come soon.

This patch turns off the flag which bans that construct, reenabling
it. The change should prevent websites from breaking.

BUG=v8:4942

Committed: https://crrev.com/7245dabdb1c4f7dc5fec06cc087e9c4180df474a
Cr-Commit-Position: refs/heads/master@{#36562}
==========

[commit-bot: I haz the power, 2016-05-27 19:14:55]

Patchset 2 (id:??) landed as
https://crrev.com/7245dabdb1c4f7dc5fec06cc087e9c4180df474a
Cr-Commit-Position: refs/heads/master@{#36562}