• littledan's avatar
    Unship ES2015 for-in initializer restrictions · 7245dabd
    littledan authored
    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
    
    Review-Url: https://codereview.chromium.org/2011223003
    Cr-Commit-Position: refs/heads/master@{#36562}
    7245dabd
Name
Last commit
Last update
..
benchmarks Loading commit data...
cctest Loading commit data...
fuzzer Loading commit data...
intl Loading commit data...
js-perf-test Loading commit data...
memory Loading commit data...
message Loading commit data...
mjsunit Loading commit data...
mozilla Loading commit data...
preparser Loading commit data...
promises-aplus Loading commit data...
simdjs Loading commit data...
test262 Loading commit data...
unittests Loading commit data...
webkit Loading commit data...
bot_default.gyp Loading commit data...
bot_default.isolate Loading commit data...
default.gyp Loading commit data...
default.isolate Loading commit data...
ignition.gyp Loading commit data...
ignition.isolate Loading commit data...
optimize_for_size.gyp Loading commit data...
optimize_for_size.isolate Loading commit data...
perf.gyp Loading commit data...
perf.isolate Loading commit data...