user0/rust
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

corrected grammar errors

Browse source
This commit is contained in:
Christian Poveda 2018-02-24 18:06:01 -05:00
parent ce3ad263ff
commit 7ded7f764c
1 changed files with 4 additions and 4 deletions
Download patch file Download diff file Expand all files Collapse all files

8
src/libcore/cell.rs
View file

@ -10,17 +10,17 @@
//! Shareable mutable containers.
//!
//! Rust memory safety is based on this rule: Given an object `T`, is only possible to
//! Rust memory safety is based on this rule: Given an object `T`, it is only possible to
//! have one of the following:
//!
//! - Having several inmutable references (`&T`) to the object (also know as Aliasing).
//! - Having several immutable references (`&T`) to the object (also know as Aliasing).
//! - Having one mutable reference (`&mut T`) to the object (also know as Mutability).
//!
//! This is enforced by the Rust compiler. However, there are situations where this rule is not
//! flexible enough. Sometimes is required to have multiple references to an object and yet
//! flexible enough. Sometimes it 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 the 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
//! `Sync`), if you need to do Aliasing and Mutation between multiple threads is possible to use