-
Notifications
You must be signed in to change notification settings - Fork 21
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Please implement Atomics.waitAsync as well! #20
Comments
I don't think that I would support adding an explicit dependency here. What is the implementation status of atomics? |
This is just an informal request for implementers to consider :)
|
Some updates:
@eqrion FYI as you're thinking about prioritizing JSPI work. |
Current semantics of JSPI should address this question. |
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: