bitvec icon indicating copy to clipboard operation
bitvec copied to clipboard

A crate for managing memory bit by bit

Results 100 bitvec issues
Sort by recently updated
recently updated
newest added

Calling `into_vec` will get a vec of the underlying data, but from what I can tell there's no way to access the "offset" at which the view into the underlying...

The documentation should mention that current methods (like get and set_aliased) when called on a type with an AtomicFoo backing will used Relaxed orderings. It would also be nice if...

Thanks for writing such a useful book to go along with `bitvec`. It's very well written and makes for enjoyable reading. Below is a diff showing a few minor changes....

This pull request updates the radium dependency to version 1.1.0, allowing me to use bitvec on a 32 bit x86 target.

e.g. no-op is spelled noöp quite a few times. not all of the misspelled words actually even need a hyphen, such as where deallocate is spelled deällocate. (I know technically...

Hello @myrrlyn bitvec: v1.0.1 I think I stumbled upon a strange and nasty bug, where the outcome is different in rustc DEV versus RELEASE compilation profile. The minimal test example...

I noticed that `Serialize` implementation of `BitVec` (and probably other types as well) uses `any::type_name()` to serialize the order. The docs for it say: > The returned string must not...

This PR adds the following methods to `BitSlice`: - `fn replace_aliased(&self, usize, bool) -> bool` - `fn replace_aliased_unchecked(&self, usize, bool) -> bool` They are modeled after the existing `fn set_aliased()`/`fn...