about summary refs log tree commit diff
diff options
context:
space:
mode:
authorJoshua Liebow-Feeser <joshlf@users.noreply.github.com>2024-03-03 07:55:23 -0800
committerGitHub <noreply@github.com>2024-03-03 07:55:23 -0800
commit59a3a5dba314d4b693d141a56fde2e6a879d0af0 (patch)
treeed53c07ec5c59e40d7c693cade5bfadf4d8b5328
parent9e73597e5a83e96e223c10b3810566c74a86a0c1 (diff)
downloadrust-59a3a5dba314d4b693d141a56fde2e6a879d0af0.tar.gz
rust-59a3a5dba314d4b693d141a56fde2e6a879d0af0.zip
Clarify atomic bit validity
The previous definition used the phrase "representation", which is ambiguous given the current state of memory model nomenclature in Rust. The new wording clarifies that size and bit validity are guaranteed to match the corresponding native integer type.
-rw-r--r--library/core/src/sync/atomic.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/library/core/src/sync/atomic.rs b/library/core/src/sync/atomic.rs
index 45193c11e1d..303f1bf8f65 100644
--- a/library/core/src/sync/atomic.rs
+++ b/library/core/src/sync/atomic.rs
@@ -2121,7 +2121,7 @@ macro_rules! atomic_int {
      $int_type:ident $atomic_type:ident) => {
         /// An integer type which can be safely shared between threads.
         ///
-        /// This type has the same in-memory representation as the underlying
+        /// This type has the same in-memory size and bit validity as the underlying
         /// integer type, [`
         #[doc = $s_int_type]
         /// `].