Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Tweak and stabilize AtomicN::fetch_update #71843

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
May 29, 2020
Merged

Tweak and stabilize AtomicN::fetch_update #71843

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
2ce3f85
Tweak and stabilize AtomicN::fetch_update
sfackler May 3, 2020
31c8205
Update src/libcore/sync/atomic.rs
sfackler May 3, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Update src/libcore/sync/atomic.rs 
Co-authored-by: Ralf Jung <[email protected]>
  • Loading branch information
@sfackler @RalfJung
sfackler and RalfJung authored May 3, 2020
commit 31c820552350e3f686a6f353982f0f31ecbaf4a7
2 changes: 1 addition & 1 deletion src/libcore/sync/atomic.rs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1807,7 +1807,7 @@ new value. Returns a `Result` of `Ok(previous_value)` if the function returned `

Note: This may call the function multiple times if the value has been changed from other threads in
the meantime, as long as the function returns `Some(_)`, but the function will have been applied
but once to the stored value.
only once to the stored value.

`fetch_update` takes two [`Ordering`] arguments to describe the memory ordering of this operation.
The first describes the required ordering for when the operation finally succeeds while the second
Expand Down