From 386b1a3c9e8634d2a2ffc3b307a3c10e8dc34697 Mon Sep 17 00:00:00 2001 From: Shaun Verch Date: Sun, 13 Aug 2023 13:54:37 -0400 Subject: [PATCH] Fix minor typo --- src/third-arc.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/third-arc.md b/src/third-arc.md index 6731269..75fd94f 100644 --- a/src/third-arc.md +++ b/src/third-arc.md @@ -12,8 +12,8 @@ list could get freed too soon! In order to get thread safety, we have to use *Arc*. Arc is completely identical to Rc except for the fact that reference counts are modified atomically. This has a bit of overhead if you don't need it, so Rust exposes both. -All we need to do to make our list is replace every reference to Rc with -`std::sync::Arc`. That's it. We're thread safe. Done! +All we need to do to make our list thread safe is replace every reference to Rc +with `std::sync::Arc`. That's it. We're thread safe. Done! But this raises an interesting question: how do we *know* if a type is thread-safe or not? Can we accidentally mess up?