summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorAndrew Banchich <andrewbanchich@gmail.com>2019-12-03 19:11:53 -0500
committerGitHub <noreply@github.com>2019-12-03 19:11:53 -0500
commit1fa948f4ccf73aa0a0d903878693c685710cd764 (patch)
treeea74085e058008763d3595949cdbd5d94e25393e
parentupdate test (diff)
downloadrust-1fa948f4ccf73aa0a0d903878693c685710cd764.tar.gz
rust-1fa948f4ccf73aa0a0d903878693c685710cd764.tar.bz2
rust-1fa948f4ccf73aa0a0d903878693c685710cd764.tar.xz
capitalize Rust
-rw-r--r--src/libcore/sync/atomic.rs2
1 files changed, 1 insertions, 1 deletions
diff --git a/src/libcore/sync/atomic.rs b/src/libcore/sync/atomic.rs
index c9ccef9..69c4aa7 100644
--- a/src/libcore/sync/atomic.rs
+++ b/src/libcore/sync/atomic.rs
@@ -27,7 +27,7 @@
27//! 27//!
28//! Atomic variables are safe to share between threads (they implement [`Sync`]) 28//! Atomic variables are safe to share between threads (they implement [`Sync`])
29//! but they do not themselves provide the mechanism for sharing and follow the 29//! but they do not themselves provide the mechanism for sharing and follow the
30//! [threading model](../../../std/thread/index.html#the-threading-model) of rust. 30//! [threading model](../../../std/thread/index.html#the-threading-model) of Rust.
31//! The most common way to share an atomic variable is to put it into an [`Arc`][arc] (an 31//! The most common way to share an atomic variable is to put it into an [`Arc`][arc] (an
32//! atomically-reference-counted shared pointer). 32//! atomically-reference-counted shared pointer).
33//! 33//!