Remove unnecessary coupling between Promise tests and Object.observe

Remove unnecessary coupling between Promise tests and Object.observe

Many mjsunit tests (as well as the promises-aplus adapter scripts) were
using Object.observe simply for microtask-enqueueing purposes. Replaced
such uses with %EnqueueMicrotask.

Committed: https://crrev.com/4b8200078a9d1d9ec5bab268d0aff6453b47ddcc
Cr-Commit-Position: refs/heads/master@{#29779}

[adamk, 2015-07-21 03:42:34]

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

[rossberg, 2015-07-21 10:25:38]

lgtm

https://codereview.chromium.org/1246933002/diff/1/test/mjsunit/es6/promises.js
File test/mjsunit/es6/promises.js (right):

https://codereview.chromium.org/1246933002/diff/1/test/mjsunit/es6/promises.j...
test/mjsunit/es6/promises.js:90: Promise.resolve().then(
Some of the tests now become a bit circular (relying on the correctness of
Promise.resolve/then to test the correctness of Promise.resolve/then). But I
don't have a better idea either.

[adamk, 2015-07-21 16:18:09]

https://codereview.chromium.org/1246933002/diff/1/test/mjsunit/es6/promises.js
File test/mjsunit/es6/promises.js (right):

https://codereview.chromium.org/1246933002/diff/1/test/mjsunit/es6/promises.j...
test/mjsunit/es6/promises.js:90: Promise.resolve().then(
On 2015/07/21 10:25:37, rossberg wrote:
> Some of the tests now become a bit circular (relying on the correctness of
> Promise.resolve/then to test the correctness of Promise.resolve/then). But I
> don't have a better idea either.

I could switch them all to use %EnqueueMicrotask, if you'd prefer.

[rossberg, 2015-07-21 16:28:43]

https://codereview.chromium.org/1246933002/diff/1/test/mjsunit/es6/promises.js
File test/mjsunit/es6/promises.js (right):

https://codereview.chromium.org/1246933002/diff/1/test/mjsunit/es6/promises.j...
test/mjsunit/es6/promises.js:90: Promise.resolve().then(
On 2015/07/21 16:18:08, adamk wrote:
> On 2015/07/21 10:25:37, rossberg wrote:
> > Some of the tests now become a bit circular (relying on the correctness of
> > Promise.resolve/then to test the correctness of Promise.resolve/then). But I
> > don't have a better idea either.
> 
> I could switch them all to use %EnqueueMicrotask, if you'd prefer.

Aw, of course. For some reason I though that can't be done, but I don't know
what I was thinking. :\  Please do.

[adamk, 2015-07-21 16:48:56]

The CQ bit was checked by adamk@chromium.org

[adamk, 2015-07-21 16:48:56]

The patchset sent to the CQ was uploaded after l-g-t-m from
rossberg@chromium.org
Link to the patchset: https://codereview.chromium.org/1246933002/#ps20001
(title: "Use %EnqueueMicrotask")

[commit-bot: I haz the power, 2015-07-21 16:49:11]

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

[commit-bot: I haz the power, 2015-07-21 17:17:02]

Committed patchset #2 (id:20001)

[commit-bot: I haz the power, 2015-07-21 17:17:17]

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