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
The stage 3 Atomics.waitAsync proposal combined with JSPI will allow Emscripten to stop busy-waiting for locks, condition variables, and other blocking synchronization primitives on the main thread, which will be a great win for performance and efficiency for large, multithreaded applications. It would be great if we could assume that the presence of JSPI implied the presence of Atomics.waitAsync across browsers so we don't have to maintain a polyfill or continue busy waiting.
The text was updated successfully, but these errors were encountered:
The stage 3
Atomics.waitAsync
proposal combined with JSPI will allow Emscripten to stop busy-waiting for locks, condition variables, and other blocking synchronization primitives on the main thread, which will be a great win for performance and efficiency for large, multithreaded applications. It would be great if we could assume that the presence of JSPI implied the presence ofAtomics.waitAsync
across browsers so we don't have to maintain a polyfill or continue busy waiting.The text was updated successfully, but these errors were encountered: