This repository has been archived by the owner on Oct 10, 2019. It is now read-only.
Normative: Permit atomic operations on BigInt64Arrays #80
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Previously, it was left up for future integration details to allow BigInt64Array and BigUint64Array to use atomic operations. This patch spells out the details of how these should work. The semantics of Atomics.wait/wake are based on doing the wait/wake on the relevant index of the underlying memory. For example, a 64-bit wait would be woken up by a 32-bit wake at twice the index. Non-atomic writes to BigInt64Arrays can be torn, following the memory model for Float64Array. In some places in internal spec names, `Int64` is replaced by `BigInt64` for consistency. Addresses #78
|
This PR got consensus at the September 2017 TC39 meeting. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Previously, it was left up for future integration details to allow
BigInt64Array and BigUint64Array to use atomic operations. This patch
spells out the details of how these should work.
The semantics of Atomics.wait/wake are based on doing the wait/wake
on the relevant index of the underlying memory. For example, a
64-bit wait would be woken up by a 32-bit wake at twice the index.
Non-atomic writes to BigInt64Arrays can be torn, following the memory
model for Float64Array.
In some places in internal spec names,
Int64is replaced byBigInt64for consistency.
Addresses #78
cc @lars-t-hansen