On 2014/03/21 20:52:19, rafaelw wrote:
It turns out the the blink dev tools needs to be able to fire a microtask
with
script on the stack. The basic idea here is if the embedder is taking
control
of
microtask delivery, it should have freedom to do what it knows is correct.
Hm, I am not sure understand. This sounds super-fishy. How can it possibly
know
that it's correct? What code would be on the stack? Dev tools would have to
know
not just that code, but the entire state of the isolate or context -- if
any of
that got mutated by somebody, it is almost impossible to guarantee that some
piece of code can't queue events. Running the queue _before_ such code has
completed would severely break the language's concurrency semantics.
https://codereview.chromium.org/205243012/
--
--
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/d/optout.
