Explain how fences interact with volatile operations #98
Conversation
This file contains hidden or 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
eldruin
reviewed
May 17, 2025
therealprof
reviewed
May 17, 2025
adamgreig
approved these changes
May 20, 2025
This was the result of a discussion with Amanieu at RustWeek. It would be nice to add more details about the planned updates (some ticket for example), and I'm not sure if this is the best place to add it to the embedonomicon. But for now, I think mentioning it here is better than nothing.
Co-authored-by: Daniel Egger <[email protected]>
jannic
force-pushed
the
explain-volatile-fence-interaction
branch
from
6e6e65b to
622f16e
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This was the result of a discussion with Amanieu at RustWeek. It would be nice to add more details about the planned updates (some ticket for example), and I'm not sure if this is the best place to add it to the embedonomicon. But for now, I think mentioning it here is better than nothing.