You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Feb 21, 2018. It is now read-only.
During the API creation process we should take WebAssembly into consideration in order to future proof what is being done now. One example is the fact that wasm will allow fine grain control over how threads are spawned.
I'm currently a member of the WebAssembly community group, but could use help making sure our progress takes advantage of the work being done there.
The text was updated successfully, but these errors were encountered:
With the multi-thread mechanism, The relationship between Environment(in node), Isolate(or Runtime in JSC) , context and thread will be very complex. Maybe, there is some restrict should be taken.
During the API creation process we should take WebAssembly into consideration in order to future proof what is being done now. One example is the fact that
wasm
will allow fine grain control over how threads are spawned.I'm currently a member of the WebAssembly community group, but could use help making sure our progress takes advantage of the work being done there.
The text was updated successfully, but these errors were encountered: