[ABANDONED] Implement Promises.

Implement Promises.

Promises provides a clean API to handle async operations.
Promises is being specified in WHATWG[1].

We implment this feature by JavaScript, Source/core/dom/Promise.js and Source/core/dom/PromiseResolver.js.
This CL doesn't include PromiseResolveHolder wrapper class, which enables C++ classes to handle a PromiseResolver.

[1] http://dom.spec.whatwg.org/#promises

BUG=243345
R=abarth

[yhirano, 2013-06-14 02:46:47]

abarth@, can you take a look at this CL?

FYI: haraken@, tyoshino@

[tyoshino (SeeGerritForStatus), 2013-06-14 04:57:53]

https://codereview.chromium.org/16838012/diff/15001/LayoutTests/fast/js/Promi...
File LayoutTests/fast/js/Promise-catch.html (right):

https://codereview.chromium.org/16838012/diff/15001/LayoutTests/fast/js/Promi...
LayoutTests/fast/js/Promise-catch.html:59: </html>
Remove L49-59?

[abarth-chromium, 2013-06-14 05:07:08]

This CL is too big to review well.  Can we break it up into smaller pieces? 
We're going to establish a number of new patterns with this work, so we should
make sure that we think about each one carefully.

I need to study this CL more carefully to understand it...  Should we start with
a simplified version?

https://codereview.chromium.org/16838012/diff/15001/Source/core/core_derived_...
File Source/core/core_derived_sources.gyp (right):

https://codereview.chromium.org/16838012/diff/15001/Source/core/core_derived_...
Source/core/core_derived_sources.gyp:632: 'action_name':
'generatePromiseCustomScript',
Can we do this with a rule rather than having a separate named action for every
JS file?  We might need to invent a new file extension like ".blinkjs" to
trigger the rule.

https://codereview.chromium.org/16838012/diff/15001/Source/core/dom/Promise.js
File Source/core/dom/Promise.js (right):

https://codereview.chromium.org/16838012/diff/15001/Source/core/dom/Promise.j...
Source/core/dom/Promise.js:35: postTask(fulfillCallback.bind(undefined,
this.associated.result));
We need to be careful about calling things like "bind" that can be modified by
the page.

https://codereview.chromium.org/16838012/diff/15001/Source/core/dom/Promise.j...
Source/core/dom/Promise.js:137: var promises =
Array.prototype.slice.call(arguments, 0);
Similarly, we don't want to depend on any statics.

https://codereview.chromium.org/16838012/diff/15001/Source/core/dom/Promise.j...
Source/core/dom/Promise.js:252: return Object.freeze($Promise);
Why Object.freeze?

https://codereview.chromium.org/16838012/diff/15001/Source/core/dom/PromiseRe...
File Source/core/dom/PromiseResolver.js (right):

https://codereview.chromium.org/16838012/diff/15001/Source/core/dom/PromiseRe...
Source/core/dom/PromiseResolver.js:34: if (this.promise === undefined ||
this.promise.state !== 'pending') {
Do you mean

"promise" in this

?

https://codereview.chromium.org/16838012/diff/15001/Source/core/dom/PromiseRe...
Source/core/dom/PromiseResolver.js:43: this.promise = undefined;
Should we call "delete this.promise" instead?

https://codereview.chromium.org/16838012/diff/15001/Source/core/page/RuntimeE...
File Source/core/page/RuntimeEnabledFeatures.in (right):

https://codereview.chromium.org/16838012/diff/15001/Source/core/page/RuntimeE...
Source/core/page/RuntimeEnabledFeatures.in:61: Promise status=experimental
Let's start off with status=test.  We can move to experimental once we've got
something complete.

[abarth-chromium, 2013-06-14 05:11:08]

Maybe a good first step is to have a Promise object with one function on it. 
That will let us work through when and how the Promise.js script gets run.  Once
we have one function, we can add more incrementally.

[yhirano, 2013-06-14 05:43:00]

https://codereview.chromium.org/16838012/diff/15001/LayoutTests/fast/js/Promi...
File LayoutTests/fast/js/Promise-catch.html (right):

https://codereview.chromium.org/16838012/diff/15001/LayoutTests/fast/js/Promi...
LayoutTests/fast/js/Promise-catch.html:59: </html>
On 2013/06/14 04:57:53, tyoshino wrote:
> Remove L49-59?

Done.

[yhirano, 2013-06-14 05:47:26]

On 2013/06/14 05:11:08, abarth wrote:
> Maybe a good first step is to have a Promise object with one function on it. 
> That will let us work through when and how the Promise.js script gets run. 
Once
> we have one function, we can add more incrementally.

I see, I will create a CL that includes
 - PromiseUtilities.{h, cpp}
 - Promise.h
 - Promise.idl which has example methods, get() and getStatic()
 - Promise.js that implements get() and getStatic()
 - Layout tests for the example methods.
as a first step.

Does it make sense?

[abarth-chromium, 2013-06-14 05:52:10]

On 2013/06/14 05:47:26, yhirano wrote:
> Does it make sense?

It's hard for me to tell.  In the first CL, I would aim for something simple
enough to understand completely.  We can do thing in large steps, it's just
going to take a while to review.  We're breaking a lot of new ground here.

[marja, 2013-06-14 07:32:04]

Please also make sure that your patch builds if you remove "#define
V8_USE_UNSAFE_HANDLES" from src/v8/include/v8.h.