update Atomic*::from_ptr and Atomic*::as_ptr docs#144072
Merged
bors merged 1 commit intorust-lang:masterfrom Jul 28, 2025
Merged
update Atomic*::from_ptr and Atomic*::as_ptr docs#144072bors merged 1 commit intorust-lang:masterfrom
Atomic*::from_ptr and Atomic*::as_ptr docs#144072bors merged 1 commit intorust-lang:masterfrom
Conversation
Collaborator
|
rustbot has assigned @Mark-Simulacrum. Use |
rustbot
added
S-waiting-on-review
library/core/src/sync/atomic.rs
Outdated
| /// through a shared reference, and can do so safely as long as they use atomic operations. Any | ||
| /// use of the returned raw pointer requires an `unsafe` block and still has to uphold the same | ||
| /// restriction: operations on it must be atomic. | ||
| /// restriction: no data races and no mixed-size accesses. |
Member
There was a problem hiding this comment.
Can we instead alter this to point at the memory model section that has more words about this? I like the wording in the from_ptr methods.
Contributor
Author
There was a problem hiding this comment.
It's restriction in [Memory model for atomic accesses]. now.
@rustbot ready
Mark-Simulacrum
added
S-waiting-on-author
rustbot
added
S-waiting-on-review
rustbot
removed
the
S-waiting-on-review
rustbot
added
the
S-waiting-on-review
Member
|
@bors r+ |
Collaborator
bors
added
S-waiting-on-bors
bors
added a commit
that referenced
this pull request
Jul 28, 2025
Rollup of 7 pull requests Successful merges: - #144072 (update `Atomic*::from_ptr` and `Atomic*::as_ptr` docs) - #144151 (`tests/ui/issues/`: The Issues Strike Back [1/N]) - #144300 (Clippy fixes for miropt-test-tools) - #144399 (Add a ratchet for moving all standard library tests to separate packages) - #144472 (str: Mark unstable `round_char_boundary` feature functions as const) - #144503 (Various refactors to the codegen coordinator code (part 3)) - #144530 (coverage: Infer `instances_used` from `pgo_func_name_var_map`) r? `@ghost` `@rustbot` modify labels: rollup
RalfJung
reviewed
Jul 28, 2025
| /// through a shared reference, and can do so safely as long as they use atomic operations. Any | ||
| /// use of the returned raw pointer requires an `unsafe` block and still has to uphold the same | ||
| /// restriction: operations on it must be atomic. | ||
| /// restriction in [Memory model for atomic accesses]. |
Member
There was a problem hiding this comment.
This doesn't sound like a sentence to me? "restriction in Memory model" is not grammatical, and also oddly capitalized.
Contributor
Author
There was a problem hiding this comment.
It's a title, so I thought it was appropriate to preserve the capitalization. The existing documentation for from_ptr uses You must adhere to the [Memory model for atomic accesses] and also uses capital letters.
Do you have any suggestions?
Member
There was a problem hiding this comment.
Something like "Any use of the returned raw pointer requires an unsafe block and still has to uphold the requirements of the [memory model]."
Member
|
(This got rolled-up so fixing the wording might need a new PR) |
rust-timer
added a commit
that referenced
this pull request
Jul 28, 2025
Rollup merge of #144072 - usamoi:docs, r=Mark-Simulacrum update `Atomic*::from_ptr` and `Atomic*::as_ptr` docs Since #128778, it's allowed to perform atomic read and non-atomic read on the same atomic at the same time. Update the `Atomic*::from_ptr` and `Atomic*::as_ptr` documentation to remove expressions such as `not allowed to mix atomic and non-atomic accesses`. see also [std::sync::atomic](https://doc.rust-lang.org/std/sync/atomic/index.html#memory-model-for-atomic-accesses)
This was referenced Jul 28, 2025
Closed
samueltardieu
added a commit
to samueltardieu/rust
that referenced
this pull request
Jul 28, 2025
fix `Atomic*::as_ptr` wording r? `@RalfJung` cc rust-lang#144072
Zalathar
added a commit
to Zalathar/rust
that referenced
this pull request
Jul 29, 2025
fix `Atomic*::as_ptr` wording r? ``@RalfJung`` cc rust-lang#144072
Zalathar
added a commit
to Zalathar/rust
that referenced
this pull request
Jul 29, 2025
fix `Atomic*::as_ptr` wording r? ```@RalfJung``` cc rust-lang#144072
Zalathar
added a commit
to Zalathar/rust
that referenced
this pull request
Jul 29, 2025
fix `Atomic*::as_ptr` wording r? ````@RalfJung```` cc rust-lang#144072
Zalathar
added a commit
to Zalathar/rust
that referenced
this pull request
Jul 29, 2025
fix `Atomic*::as_ptr` wording r? `````@RalfJung````` cc rust-lang#144072
github-actions bot
pushed a commit
to model-checking/verify-rust-std
that referenced
this pull request
Jul 30, 2025
update `Atomic*::from_ptr` and `Atomic*::as_ptr` docs Since rust-lang#128778, it's allowed to perform atomic read and non-atomic read on the same atomic at the same time. Update the `Atomic*::from_ptr` and `Atomic*::as_ptr` documentation to remove expressions such as `not allowed to mix atomic and non-atomic accesses`. see also [std::sync::atomic](https://doc.rust-lang.org/std/sync/atomic/index.html#memory-model-for-atomic-accesses)
github-actions bot
pushed a commit
to model-checking/verify-rust-std
that referenced
this pull request
Jul 30, 2025
fix `Atomic*::as_ptr` wording r? `````@RalfJung````` cc rust-lang#144072
github-actions bot
pushed a commit
to rust-lang/rustc-dev-guide
that referenced
this pull request
Jul 31, 2025
fix `Atomic*::as_ptr` wording r? `````@RalfJung````` cc rust-lang/rust#144072
Kobzol
pushed a commit
to Kobzol/rustc_codegen_gcc
that referenced
this pull request
Dec 21, 2025
Rollup of 7 pull requests Successful merges: - rust-lang/rust#144072 (update `Atomic*::from_ptr` and `Atomic*::as_ptr` docs) - rust-lang/rust#144151 (`tests/ui/issues/`: The Issues Strike Back [1/N]) - rust-lang/rust#144300 (Clippy fixes for miropt-test-tools) - rust-lang/rust#144399 (Add a ratchet for moving all standard library tests to separate packages) - rust-lang/rust#144472 (str: Mark unstable `round_char_boundary` feature functions as const) - rust-lang/rust#144503 (Various refactors to the codegen coordinator code (part 3)) - rust-lang/rust#144530 (coverage: Infer `instances_used` from `pgo_func_name_var_map`) r? `@ghost` `@rustbot` modify labels: rollup
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
5 participants
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.
Since #128778, it's allowed to perform atomic read and non-atomic read on the same atomic at the same time. Update the
Atomic*::from_ptrandAtomic*::as_ptrdocumentation to remove expressions such asnot allowed to mix atomic and non-atomic accesses.see also std::sync::atomic