From 8f1296a68ed173b7d14f328c1128f5da8b29b96b Mon Sep 17 00:00:00 2001 From: Shiv Dhar Date: Thu, 26 Oct 2023 18:49:00 +0530 Subject: [PATCH] [docs] make readme clearer w.r.t. atomic synchronization overhead --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index dfe5ae1a..0d593ae8 100644 --- a/README.md +++ b/README.md @@ -364,7 +364,7 @@ restore the ones you need. atomic capability, and targets that do not possess atomic instructions can still function with this feature *enabled*. Its only effect is that targets which do have atomic instructions may choose to disable it and enforce - single-threaded behavior that never incurs atomic synchronization. + single-threaded behavior that never incurs the cost of atomic synchronization. - `serde`: This enables the de/serialization of `bitvec` buffers through the `serde` system. This can be useful if you need to transmit `usize => bool`