From: Deepak Sirone Date: Tue, 7 Jun 2016 03:47:49 +0000 (+0530) Subject: Fixed sahred -> shared typo X-Git-Url: https://git.ralfj.de/rust-101.git/commitdiff_plain/53b9ab56f7b712e6710fd873d456a0fe1f13b785?hp=-c Fixed sahred -> shared typo --- 53b9ab56f7b712e6710fd873d456a0fe1f13b785 diff --git a/src/part12.rs b/src/part12.rs index 34e994e..62f0868 100644 --- a/src/part12.rs +++ b/src/part12.rs @@ -92,7 +92,7 @@ fn demo_cell(c: &mut Callbacks) { //@ Putting it all together, the story around mutation and ownership through references looks as follows: There are *unique* references, //@ which - because of their exclusivity - are always safe to mutate through. And there are *shared* references, where the compiler cannot //@ generally promise that mutation is safe. However, if extra circumstances guarantee that mutation *is* safe, then it can happen even -//@ through a sahred reference - as we saw with `Cell`. +//@ through a shared reference - as we saw with `Cell`. // ## `RefCell` //@ As the next step in the evolution of `Callbacks`, we could try to solve this problem of mutability once and for all, by adding `Cell`