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 Jun 22, 2023. It is now read-only.
After timeout milliseconds has passed, perform the following actions concurrently:
The actions here seem to avoid directly running JavaScript, which shouldn't be run concurrently with other JavaScript in the same agent. In particular:
In the Atomics.wait case, a record field will be set, which will then be read by the other agent once it's resumed. This also seems fine, though it seems more complicated without adding any particular clarity compared to what we have currently in the JS spec.
Let's think about what's the clearest way to phrase all of this. This editorial issue does not block Stage 3, but I'd like to think it through before merging into the main spec.
The text was updated successfully, but these errors were encountered:
The spec text for AddAlarm contains:
The actions here seem to avoid directly running JavaScript, which shouldn't be run concurrently with other JavaScript in the same agent. In particular:
Atomics.wait
case, a record field will be set, which will then be read by the other agent once it's resumed. This also seems fine, though it seems more complicated without adding any particular clarity compared to what we have currently in the JS spec.Let's think about what's the clearest way to phrase all of this. This editorial issue does not block Stage 3, but I'd like to think it through before merging into the main spec.
The text was updated successfully, but these errors were encountered: