Make atomic peek/poke unstable and opt-in #13888
Merged
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.
We're not ready to stabilize
peek()
/poke()
atomic operations, somove them into an unstable opt-in
PeekPoke
module. The oldavailable-by-default versions are deprecated and the new versions are
available with
use PeekPoke
.This also corrects the documentation to note that
peek()
/poke()
arenot atomic.
Closes #13827
Closes https://github.com/Cray/chapel-private/issues/392