Bug 241414 – [JSC] Add support for Atomics.waitAsync

• Status: RESOLVED
• Resolution: FIXED
• Component: JavaScriptCore

[Florens Verschelde]

We at StackBlitz are using Atomics.waitAsync (https://github.com/tc39/proposal-atomics-wait-async, apparently stage 3 and shipped in Chromium) on stackblitz.com to power our Node.js-in-the-browser port (called WebContainers).

Firefox doesn't implement Atomics.waitAsync either, but we were able to implement a polyfill using workers-in-workers, something that is not possible in Safari at this time.

The lack of Atomics.waitAsync in WebKit is one of the things stopping us from offering WebContainers to users of Safari and other WebKit-based browsers at this time. (Others include bug 174931, bug 238442, and possibly more we haven't identified yet.)

[Florens Verschelde]

Firefox is currently prototyping:
https://groups.google.com/a/mozilla.org/g/dev-platform/c/Z5TPivxh1Xs

[Radar WebKit Bug Importer]

<rdar://problem/94655073>

[Simon Chang]

Given that this bug is also relevant to the implementation of RegExp lookbehind, please also take time to look at https://bugs.webkit.org/show_bug.cgi?id=174931 which is also needed for a higher priority. It's also noted that Atomics.waitAsync has been shipped in both Chromium and Firefox now.

[Yijia Huang]

*** Bug 245676 has been marked as a duplicate of this bug. ***

[Yijia Huang]

Pull request: https://github.com/WebKit/WebKit/pull/5333

[Yijia Huang]

Pull request: https://github.com/WebKit/WebKit/pull/5683

[EWS]

Committed 257061@main (7e3fb31d5987): <https://commits.webkit.org/257061@main>

Reviewed commits have been landed. Closing PR #5333 and removing active labels.