about summary refs log tree commit diff
diff options
context:
space:
mode:
authorJúnior Bassani <junior.eduardo.bassani@gmail.com>2021-07-06 10:53:14 -0300
committerJúnior Bassani <junior.eduardo.bassani@gmail.com>2021-07-06 10:53:14 -0300
commit0d61e6e8d68be269c57d1d067f29a8a0e5eb6e29 (patch)
tree085c621fd2e11d006d838902a1d2c5dc6fa60955
parenta87fb1802761ee51b2f9f8928e50c27c6b64ab9c (diff)
downloadrust-0d61e6e8d68be269c57d1d067f29a8a0e5eb6e29.tar.gz
rust-0d61e6e8d68be269c57d1d067f29a8a0e5eb6e29.zip
Fix typo in core::sync::atomic::compiler_fence example
-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 3f5c10b02eb..b673b36c102 100644
--- a/library/core/src/sync/atomic.rs
+++ b/library/core/src/sync/atomic.rs
@@ -2714,7 +2714,7 @@ pub fn fence(order: Ordering) {
 /// Without `compiler_fence`, the `assert_eq!` in following code
 /// is *not* guaranteed to succeed, despite everything happening in a single thread.
 /// To see why, remember that the compiler is free to swap the stores to
-/// `IMPORTANT_VARIABLE` and `IS_READ` since they are both
+/// `IMPORTANT_VARIABLE` and `IS_READY` since they are both
 /// `Ordering::Relaxed`. If it does, and the signal handler is invoked right
 /// after `IS_READY` is updated, then the signal handler will see
 /// `IS_READY=1`, but `IMPORTANT_VARIABLE=0`.