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.
This commit is contained in:
Joshua Liebow-Feeser 2024-03-03 07:55:23 -08:00 committed by GitHub
parent 9e73597e5a
commit 59a3a5dba3
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -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]
/// `].