Clarity change: make it clear that Atomics.notify() always causes Atomics.wait() to return #37742
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Atomics.wait()
will never move on unless the expected value changes ("As long as that is true, it will not go on")Atomics.wait()
can return which valueMotivation
I wasted many hours debugging an intermittent issue with a SharedArrayBuffer system due to an initial misinterpretation of MDN docs. I eventually opened a bug ticket in Bugzilla, and the behavior was clarified by André Bargull.
Additional details