Remove --harmony-* flags for new Object static methods

Remove --harmony-* flags for new Object static methods

Both --harmony-object-values-entries and --harmony-object-own-property-descriptors
are on by default in v8 5.4, which has now shipped to
stable as Chrome 54.

R=caitp@igalia.com

Committed: https://crrev.com/a1381990a7e6cb86e6f009b62fce7c9fe010722f
Cr-Commit-Position: refs/heads/master@{#40683}

[adamk, 2016-10-31 21:34:59]

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

[commit-bot: I haz the power, 2016-10-31 21:35:01]

Dry run: CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[caitp, 2016-10-31 21:37:20]

lgtm

https://codereview.chromium.org/2464733003/diff/1/test/mjsunit/object-entries.js
File test/mjsunit/object-entries.js (left):

https://codereview.chromium.org/2464733003/diff/1/test/mjsunit/object-entries...
test/mjsunit/object-entries.js:6: // Flags: --allow-natives-syntax
Don't we normally put these in the es6/ or es7/ or whatever subdirectories when
shipping or removing the flag? Or has that convention disappeared?

[adamk, 2016-10-31 21:39:46]

https://codereview.chromium.org/2464733003/diff/1/test/mjsunit/object-entries.js
File test/mjsunit/object-entries.js (left):

https://codereview.chromium.org/2464733003/diff/1/test/mjsunit/object-entries...
test/mjsunit/object-entries.js:6: // Flags: --allow-natives-syntax
On 2016/10/31 21:37:20, caitp wrote:
> Don't we normally put these in the es6/ or es7/ or whatever subdirectories
when
> shipping or removing the flag? Or has that convention disappeared?

You caught me :)

I couldn't remember which version these features were in. If you can tell me
which version it'll be I can move them, but I think this may be more bookkeeping
than it's worth. Interested in hearing if you feel this distinction is still
useful.

[commit-bot: I haz the power, 2016-10-31 22:05:05]

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

[commit-bot: I haz the power, 2016-10-31 22:05:06]

Dry run: This issue passed the CQ dry run.

[caitp, 2016-10-31 22:11:23]

https://codereview.chromium.org/2464733003/diff/1/test/mjsunit/object-entries.js
File test/mjsunit/object-entries.js (left):

https://codereview.chromium.org/2464733003/diff/1/test/mjsunit/object-entries...
test/mjsunit/object-entries.js:6: // Flags: --allow-natives-syntax
On 2016/10/31 21:39:46, adamk wrote:
> On 2016/10/31 21:37:20, caitp wrote:
> > Don't we normally put these in the es6/ or es7/ or whatever subdirectories
> when
> > shipping or removing the flag? Or has that convention disappeared?
> 
> You caught me :)
> 
> I couldn't remember which version these features were in. If you can tell me
> which version it'll be I can move them, but I think this may be more
bookkeeping
> than it's worth. Interested in hearing if you feel this distinction is still
> useful.

They've all missed the 7.0 boat, which puts them at... ECMA2016? I think it's
fine to put them in the es7  folder though, since that's how most people think
of them

[adamk, 2016-10-31 22:27:37]

On 2016/10/31 22:11:23, caitp wrote:
>
https://codereview.chromium.org/2464733003/diff/1/test/mjsunit/object-entries.js
> File test/mjsunit/object-entries.js (left):
> 
>
https://codereview.chromium.org/2464733003/diff/1/test/mjsunit/object-entries...
> test/mjsunit/object-entries.js:6: // Flags: --allow-natives-syntax
> On 2016/10/31 21:39:46, adamk wrote:
> > On 2016/10/31 21:37:20, caitp wrote:
> > > Don't we normally put these in the es6/ or es7/ or whatever subdirectories
> > when
> > > shipping or removing the flag? Or has that convention disappeared?
> > 
> > You caught me :)
> > 
> > I couldn't remember which version these features were in. If you can tell me
> > which version it'll be I can move them, but I think this may be more
> bookkeeping
> > than it's worth. Interested in hearing if you feel this distinction is still
> > useful.
> 
> They've all missed the 7.0 boat, which puts them at... ECMA2016? I think it's
> fine to put them in the es7  folder though, since that's how most people think
> of them

I think it's actually 2017 (2016 is just exponentiation and
Array.prototype.includes), so this would be es8. I guess I'll create that
directory for now, we can always remove it later.

[adamk, 2016-10-31 22:28:38]

The CQ bit was checked by adamk@chromium.org

[adamk, 2016-10-31 22:28:38]

The patchset sent to the CQ was uploaded after l-g-t-m from caitp@igalia.com
Link to the patchset: https://codereview.chromium.org/2464733003/#ps20001
(title: "Move tests to es8")

[commit-bot: I haz the power, 2016-10-31 22:28:45]

CQ is trying da patch. Follow status at
 
https://chromium-cq-status.appspot.com/v2/patch-status/codereview.chromium.or...

[commit-bot: I haz the power, 2016-10-31 22:53:03]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2016-11-17 22:18:37]

Description was changed from

==========
Remove --harmony-* flags for new Object static methods

Both --harmony-object-values-entries and
--harmony-object-own-property-descriptors
are on by default in v8 5.4, which has now shipped to
stable as Chrome 54.

R=caitp@igalia.com
==========

to

==========
Remove --harmony-* flags for new Object static methods

Both --harmony-object-values-entries and
--harmony-object-own-property-descriptors
are on by default in v8 5.4, which has now shipped to
stable as Chrome 54.

R=caitp@igalia.com

Committed: https://crrev.com/a1381990a7e6cb86e6f009b62fce7c9fe010722f
Cr-Commit-Position: refs/heads/master@{#40683}
==========

[commit-bot: I haz the power, 2016-11-17 22:18:39]

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