From 4895f8d36dc49f6aa6c96efd00914da1595602b2 Mon Sep 17 00:00:00 2001 From: EricLBuehler Date: Sun, 9 Jul 2023 05:51:46 -0400 Subject: [PATCH] Update readme --- README.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/README.md b/README.md index 6feed7d..271e898 100644 --- a/README.md +++ b/README.md @@ -17,9 +17,8 @@ A `Weak` is a non-owning reference to the data held by a `Trc`. They break reference cycles by adding a layer of indirection and act as an observer. They cannot even access the data directly, and must be converted back into `Trc`. `Weak` does not keep the value alive (whcih can be dropped), and only keeps the backing allocation alive. -To soundly implement thread safety `Trc` does not itself implement [`Send`] or [`Sync`]. However, `SharedTrc` does, and it is the only way to safely send a `Trc` across threads. See `SharedTrc` for it's API, which is similar to that of `Weak`. +To soundly implement thread safety `Trc` does not itself implement `Send` or `Sync`. However, `SharedTrc` does, and it is the only way to safely send a `Trc` across threads. See `SharedTrc` for it's API, which is similar to that of `Weak`. -`Trc` will automatically compile to use either locks or atomics, depending on the system. ## Examples