From: Ralf Jung Date: Fri, 28 Apr 2023 13:43:48 +0000 (+0200) Subject: Merge pull request #41 from bzindovic/bzindovic-part13-clarity-fix X-Git-Url: https://git.ralfj.de/rust-101.git/commitdiff_plain/8eb07931e8a0427fd63cd2245602858881279a2c?hp=de20ea2de7cb19c2c379fcd61279e13da9c8193d Merge pull request #41 from bzindovic/bzindovic-part13-clarity-fix Fix grammar to improve clarity --- diff --git a/src/part13.rs b/src/part13.rs index 31f629b..ac7698c 100644 --- a/src/part13.rs +++ b/src/part13.rs @@ -198,7 +198,7 @@ pub fn main() { //@ functions provided by `Send`. What the trait says is that types which are `Send` can be safely //@ sent to another thread without causing trouble. //@ Of course, all the primitive data-types are `Send`. So is `Arc`, which is why Rust accepted our -//@ code. But `Rc` is not `Send`, and for a good reason! If had two `Rc` to the same data, and sent +//@ code. But `Rc` is not `Send`, and for a good reason! If we had two `Rc`s to the same data, and sent //@ one of them to another thread, things could go havoc due to the lack of synchronization. //@ //@ Now, `Send` as a trait is fairly special. It has a so-called *default implementation*. This