summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChristian Poveda <christianpoveda@protonmail.com>2018-02-23 15:12:28 -0500
committerChristian Poveda <christianpoveda@protonmail.com>2018-02-23 15:12:28 -0500
commit43de01f97eeee13f9bf9f19b0b241e8368633d11 (patch)
treeb01c051649f7b38581922def223d4c043723ae3f
parent58d1f839520b97ac06e48aeb49d814282b20056c (diff)
downloadrust-43de01f97eeee13f9bf9f19b0b241e8368633d11.tar.gz
cleaned trailing whitespaces
-rw-r--r--src/libcore/cell.rs4
1 files changed, 2 insertions, 2 deletions
diff --git a/src/libcore/cell.rs b/src/libcore/cell.rs
index b3a7d20c4aa..6f0655f2033 100644
--- a/src/libcore/cell.rs
+++ b/src/libcore/cell.rs
@@ -20,9 +20,9 @@
//! flexible enough. Sometimes is required to have multiple references to an object and yet
//! mutate it.
//!
-//! Shareable mutable containers exist to permit mutability in presence of aliasing in a
+//! Shareable mutable containers exist to permit mutability in presence of aliasing in a
//! controlled manner. Both `Cell<T>` and `RefCell<T>` allows to do this in a single threaded
-//! way. However, neither `Cell<T>` nor `RefCell<T>` are thread safe (they do not implement
+//! way. However, neither `Cell<T>` nor `RefCell<T>` are thread safe (they do not implement
//! `Sync`), if you need to do Aliasing and Mutation between multiple threads is possible to use
//! `Mutex`, `RwLock` or `AtomicXXX`.
//!