Ok. All done and ready for review again.

Note that this patch now has https://codereview.chromium.org/131413008/ rolled into it along with per-isolate storage (isolate->heap()->microtask_state()) and
a per-isolate cctest.


https://codereview.chromium.org/154283002/diff/20001/include/v8.h
File include/v8.h (right):

https://codereview.chromium.org/154283002/diff/20001/include/v8.h#newcode3862
include/v8.h:3862: typedef void (*MicrotaskCallback)();
On 2014/02/10 14:22:02, Sven Panne wrote:
We should probably add an Isolate* parameter. Every time we didn't add
one for
callbacks, we regretted it later...

Done.

https://codereview.chromium.org/154283002/diff/20001/include/v8.h#newcode4585
include/v8.h:4585: * Runs the Microtask Work Queue until empty
On 2014/02/10 14:09:01, rossberg wrote:
The new functions could use comments pointing out that they're
experimental for
the time being.

Done.

https://codereview.chromium.org/154283002/diff/20001/test/cctest/test-api.cc
File test/cctest/test-api.cc (right):

https://codereview.chromium.org/154283002/diff/20001/test/cctest/test-api.cc#newcode20553
test/cctest/test-api.cc:20553: void ExternalMicrotaskOne() {
On 2014/02/10 14:22:02, Sven Panne wrote:
Nit: static. Reduces the probability of linker clashes for cctest.

Done.

https://codereview.chromium.org/154283002/diff/20001/test/cctest/test-api.cc#newcode20554
test/cctest/test-api.cc:20554: v8::HandleScope scope(CcTest::isolate());
On 2014/02/10 14:22:03, Sven Panne wrote:
Calling CcTest::isolate() is a strong indicator that the callbacks
should
probably get an Isolate* argument. CcTest::isolate() is an ugly hack
(basically
Isolate::Current() in disguise) and already scheduled for removal. :-)

Good to know. Done.

https://codereview.chromium.org/154283002/

--
--
v8-dev mailing list
[email protected]
http://groups.google.com/group/v8-dev
--- You received this message because you are subscribed to the Google Groups "v8-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.

Reply via email to