"fetch a module script tree" is asynchronous #230
Assignees
Labels
Comments
bfgeek
added a commit
that referenced
this issue
Apr 6, 2017
Instead of relying on "in parallel" this change makes all the thread hopping explicit via. message passing and queue tasks on the appropriate event loop. - Fixes #372, changes arguments to fetch a module script graph. - Fixes #370, running scripts in parallel. Now the script explicitly are run within a task queued on the worklet global scope's event loop. - Fixes #318, actually runs the event loop. - Fixes #230, treats "fetch a module worker script graph" as asynchronous. - Probably fixes #225 ? I think I'm grabbing the correct state at each thread hop.
bfgeek
added a commit
that referenced
this issue
Apr 11, 2017
* [worklets] Multiple fixes to the {{Worklet/import()}} algorithm.
Instead of relying on "in parallel" this change makes all the thread
hopping explicit via. message passing and queue tasks on the appropriate
event loop.
- Fixes #372, changes arguments to fetch a module script graph.
- Fixes #370, running scripts in parallel. Now the script explicitly are
run within a task queued on the worklet global scope's event loop.
- Fixes #318, actually runs the event loop.
- Fixes #230, treats "fetch a module worker script graph" as
asynchronous.
- Probably fixes #225 ? I think I'm grabbing the correct state at each
thread hop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The specification assumes it isn't. @bzbarsky
The text was updated successfully, but these errors were encountered: