@@ -563,8 +563,8 @@ impl AtomicBool {
563
563
/// `align_of::<AtomicBool>() == 1`).
564
564
/// * `ptr` must be [valid] for both reads and writes for the whole lifetime `'a`.
565
565
/// * You must adhere to the [Memory model for atomic accesses]. In particular, it is not
566
- /// allowed to mix atomic and non-atomic accesses, or atomic accesses of different sizes,
567
- /// without synchronization.
566
+ /// allowed to mix conflicting atomic and non-atomic accesses, or atomic accesses of different
567
+ /// sizes, without synchronization.
568
568
///
569
569
/// [valid]: crate::ptr#safety
570
570
/// [Memory model for atomic accesses]: self#memory-model-for-atomic-accesses
@@ -1246,7 +1246,7 @@ impl AtomicBool {
1246
1246
/// atomic types work with interior mutability. All modifications of an atomic change the value
1247
1247
/// through a shared reference, and can do so safely as long as they use atomic operations. Any
1248
1248
/// use of the returned raw pointer requires an `unsafe` block and still has to uphold the same
1249
- /// restriction: operations on it must be atomic .
1249
+ /// restriction: no data races and no mixed-size accesses .
1250
1250
///
1251
1251
/// # Examples
1252
1252
///
@@ -1519,8 +1519,8 @@ impl<T> AtomicPtr<T> {
1519
1519
/// can be bigger than `align_of::<*mut T>()`).
1520
1520
/// * `ptr` must be [valid] for both reads and writes for the whole lifetime `'a`.
1521
1521
/// * You must adhere to the [Memory model for atomic accesses]. In particular, it is not
1522
- /// allowed to mix atomic and non-atomic accesses, or atomic accesses of different sizes,
1523
- /// without synchronization.
1522
+ /// allowed to mix conflicting atomic and non-atomic accesses, or atomic accesses of different
1523
+ /// sizes, without synchronization.
1524
1524
///
1525
1525
/// [valid]: crate::ptr#safety
1526
1526
/// [Memory model for atomic accesses]: self#memory-model-for-atomic-accesses
@@ -2488,7 +2488,7 @@ impl<T> AtomicPtr<T> {
2488
2488
/// atomic types work with interior mutability. All modifications of an atomic change the value
2489
2489
/// through a shared reference, and can do so safely as long as they use atomic operations. Any
2490
2490
/// use of the returned raw pointer requires an `unsafe` block and still has to uphold the same
2491
- /// restriction: operations on it must be atomic .
2491
+ /// restriction: no data races and no mixed-size accesses .
2492
2492
///
2493
2493
/// # Examples
2494
2494
///
@@ -2696,8 +2696,8 @@ macro_rules! atomic_int {
2696
2696
} ]
2697
2697
/// * `ptr` must be [valid] for both reads and writes for the whole lifetime `'a`.
2698
2698
/// * You must adhere to the [Memory model for atomic accesses]. In particular, it is not
2699
- /// allowed to mix atomic and non-atomic accesses, or atomic accesses of different sizes,
2700
- /// without synchronization.
2699
+ /// allowed to mix conflicting atomic and non-atomic accesses, or atomic accesses of different
2700
+ /// sizes, without synchronization.
2701
2701
///
2702
2702
/// [valid]: crate::ptr#safety
2703
2703
/// [Memory model for atomic accesses]: self#memory-model-for-atomic-accesses
@@ -3618,7 +3618,7 @@ macro_rules! atomic_int {
3618
3618
/// atomic types work with interior mutability. All modifications of an atomic change the value
3619
3619
/// through a shared reference, and can do so safely as long as they use atomic operations. Any
3620
3620
/// use of the returned raw pointer requires an `unsafe` block and still has to uphold the same
3621
- /// restriction: operations on it must be atomic .
3621
+ /// restriction: no data races and no mixed-size accesses .
3622
3622
///
3623
3623
/// # Examples
3624
3624
///
0 commit comments