Skip to content
This repository has been archived by the owner on Jun 22, 2023. It is now read-only.

Editorial: Wording for running concurrently #17

Open
littledan opened this issue Jun 27, 2019 · 0 comments
Open

Editorial: Wording for running concurrently #17

littledan opened this issue Jun 27, 2019 · 0 comments

Comments

@littledan
Copy link
Member

The spec text for AddAlarm contains:

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:

  • Call() will be used on a JavaScript function, but this may be avoided by the fix to Editorial: Alarm functions mechanism is confusing and gratuitous #15
  • 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.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant