Skip to content

[docs] make readme clearer w.r.t. atomic synchronization overhead #248

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
shivdhar wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[docs] make readme clearer w.r.t. atomic synchronization overhead #248

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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`
Expand Down