Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(331)

Issue 693153004: Remove --harmony implications for incomplete features (Closed)

Created:
6 years, 1 month ago by rossberg
Modified:
6 years, 1 month ago
Reviewers:
adamk
CC:
arv (Not doing code reviews), Dmitry Lomov (no reviews), v8-dev
Project:
v8
Visibility:
Public.

Description

Remove --harmony implications for incomplete features This is in preparation for making --harmony and --es-staging synonyms. The only remaining difference currently is block-scoping, which is still implied by --harmony, to avoid regressing on a long-available feature. Also removes the special-casing of --harmony-proxies. R=adamk@chromium.org BUG= Committed: https://code.google.com/p/v8/source/detail?r=25115

Patch Set 1 #

Unified diffs Side-by-side diffs Delta from patch set Stats (+45 lines, -41 lines) Patch
M src/bootstrapper.cc View 7 chunks +13 lines, -19 lines 0 comments Download
M src/flag-definitions.h View 2 chunks +30 lines, -20 lines 0 comments Download
M test/mjsunit/harmony/classes.js View 1 chunk +1 line, -1 line 0 comments Download
M test/mjsunit/harmony/regress/regress-343928.js View 1 chunk +1 line, -1 line 0 comments Download

Messages

Total messages: 3 (0 generated)
rossberg
6 years, 1 month ago (2014-10-31 15:09:53 UTC) #1
adamk
lgtm I also like the "INPROGRESS" tag, much better than what blink calls this ("experimental"). ...
6 years, 1 month ago (2014-11-03 17:50:04 UTC) #2
rossberg
6 years, 1 month ago (2014-11-04 16:05:38 UTC) #3
Message was sent while issue was closed.
Committed patchset #1 manually as 25115 (presubmit successful).

Powered by Google App Engine
This is Rietveld 408576698