Skip to content

Commit 4474385

Browse files
564: inherent mutability -> interior mutability r=cuviper a=MajorBreakfast It's called "interior" mutability not "inherent" mutability. Old PR of mine that already fixed this once 😄 rayon-rs#458 Section in the book https://doc.rust-lang.org/book/second-edition/ch15-05-interior-mutability.html Co-authored-by: Josef Brandl <[email protected]>
2 parents 717f193 + 6455376 commit 4474385

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

FAQ.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -196,7 +196,7 @@ these are preferable to random failures in my experience.
196196
## But wait, isn't Rust supposed to free me from this kind of thinking?
197197

198198
You might think that Rust is supposed to mean that you don't have to
199-
think about atomicity at all. In fact, if you avoid inherent
199+
think about atomicity at all. In fact, if you avoid interior
200200
mutability (`Cell` and `RefCell` in a sequential setting, or
201201
`AtomicUsize`, `RwLock`, `Mutex`, et al. in parallel code), then this
202202
is true: the type system will basically guarantee that you don't have

0 commit comments

Comments
 (0)