AuroraMiddleware/v8
1
0
Fork 0
Code Issues 2 Pull Requests Releases Wiki Activity
59,971 Commits 1 Branch 0 Tags 839 MiB
7ec8b6b9ee
Commit Graph

9 Commits

Author SHA1 Message Date
adamk
624bc966b3 Super property loads and stores should throw if [[Prototype]] is null 
While fixing the bug, removed code duplication from super load/store
runtime calls, and inlined calls of Object::ReadAbsentProperty (left
over from strong mode).

BUG=v8:5335

Review-Url: https://codereview.chromium.org/2311413002
Cr-Commit-Position: refs/heads/master@{#39257}
 2016-09-07 17:14:14 +00:00
adamk
a0a8ecd078 Remove runtime flags for sloppy mode block scoping features 
These were all on by default in M49 without complaint.

R=littledan@chromium.org

Review URL: https://codereview.chromium.org/1858943002

Cr-Commit-Position: refs/heads/master@{#35342}
 2016-04-08 00:30:20 +00:00
adamk
dea9559457 Remove destructuring and default arguments runtime flags 
These flags have been on by default since version 4.9, which has been
in stable Chrome for over a week now, demonstrating that they're
here to stay.

Also moved the tests out of harmony/ and into es6/.

Review URL: https://codereview.chromium.org/1776683003

Cr-Commit-Position: refs/heads/master@{#34692}
 2016-03-10 23:22:30 +00:00
adamk
5ceb4feca3 Remove always-on --harmony-rest-parameters flag 
It shipped in Chrome 47.

Review URL: https://codereview.chromium.org/1519073004

Cr-Commit-Position: refs/heads/master@{#32816}
 2015-12-12 00:00:38 +00:00
adamk
7d1d978654 Rename destructuring flag to "--harmony-destructuring-bind" 
This is in preparation for the addition of --harmony-destructuring-assignment.

BUG=v8:811
LOG=n

Review URL: https://codereview.chromium.org/1450193002

Cr-Commit-Position: refs/heads/master@{#32098}
 2015-11-18 23:30:09 +00:00
ishell
059478165c [es6] Fix Object built-in subclassing. 
BUG=v8:3886
LOG=Y

Review URL: https://codereview.chromium.org/1422853004

Cr-Commit-Position: refs/heads/master@{#31760}
 2015-11-03 18:20:44 +00:00
neis
b5d0e31582 Fix another corner-case behavior of Object::SetSuperProperty. 
If the property is a data property on the holder (or does not exist) and is a readonly data property in the receiver, then we must fail.

R=rossberg, verwaest@chromium.org
BUG=

Review URL: https://codereview.chromium.org/1424233005

Cr-Commit-Position: refs/heads/master@{#31751}
 2015-11-03 14:53:09 +00:00
neis
8c1377a5b4 Fix corner-case behavior of Object::SetSuperProperty. 
When the property is an accessor property in the receiver but not on the
holder (ES6 "target"), we must fail.

R=rossberg, verwaest@chromium.org
BUG=

Review URL: https://codereview.chromium.org/1427113002

Cr-Commit-Position: refs/heads/master@{#31733}
 2015-11-03 08:04:32 +00:00
adamk
a4689fc21f Remove flags for spread calls and arrays 
These features shipped in M46 without issue.

Review URL: https://codereview.chromium.org/1429653006

Cr-Commit-Position: refs/heads/master@{#31635}
 2015-10-28 15:57:27 +00:00