A conventional, compact and core (no_std) bitmap.
You are recommended to use this crate when you want to maintain a bitmap containing a large but fixed number of bits.
For example, you may want to manage a set of resources, which can be described by two states, and a bitmap is fit for you.
If you want to maintain a small set of flags, like 2 or 3, we recommend flagset instead.
Also, bitset-core is
an earlier yet powerful crate that implemented bitset trait.
However, the implementation between bitset-core
and cbitmap
is quiet different.
What's more, the performance of cbitmap
has not been tested
since it's on alpha version. If you care most about performance,
please make a careful consideration before choice.
We have provided a crate::bitmap::Bitmap
type:
rust
pub struct Bitmap<const BYTES: usize> {
bits: [u8; BYTES],
}
You are recommended to use macros to create new bitmaps:
```rust use cbitmap::bitmap::*;
let map = newmap!(0b_01; 2); ```
See also crate::he_lang
.
The bitmap can be manipulated in conventional ways, like
Bitmap::test()
,
Bitmap::set()
,
Bitmap::reset()
,
Bitmap::flip()
and
Bitmap::at()
.
Please see the documentation for
detailed examples.
The bitmap is actually a wrapper of u8
array [u8; BYTES]
.
It can be put on diverse places on memory. For example, if
the map is relatively small like 8 or 16 bits,
you can put it on stack safely. If it is larger like 256 or
1024 bits, you may want to put it on heap.
Here is a simple example:
```rust use cbitmap::bitmap::*;
// A macro are provided to create a bitmap. let mut map = newmap!(;16);
// There is a set of methods to manipulate the bitmap: map.set(10); map.reset(10); map.flip(10);
// Some C++ like methods are provided: asserteq!(map.test(10), true); asserteq!(map.any(), true); assert_eq!(map.none(), false);
// Also provide other useful methods: asserteq!(map.findfirst_one(), 10);
// You can access a single bit using wrappers: let mut bit = map.atmut(10); asserteq!(bit, true); bit.flip(); assert_eq!(map.at(10), false); ```
Please see the documentation of Bitmap
and
the examples dir for detailed examples.
You can use cargo run --example <name>
to run the examples we
provide. A simple example is bitmap-base
, another extensive
example about practical usage is bitmap-usecase
, where bitmap
is used to manage raw memory resources.
The bitmap is specified with its size-in-bytes by BYTES
. This
is slightly different from conventional bitset<N>
in C++,
where N
indicating the size-in-bits. We implemented bitmap
in this way to stay on rust-stable, where the
#![feature(generic_const_exprs)]
is not supported yet, thus,
it is not allowed to do like this:
rust
// requiring #![feature(generic_const_exprs)]
pub struct Bitmap<const N: usize> {
bits: [u8; (N + 7) / 8],
}
We have provided an alternative way to let you specify the size
in bits. The macro crate::newmap
achieves this:
rust
const BITS: usize = 16;
let map = newmap!(;BITS);
let another = newmap!(;BITS * 2);
In principle, it is nevertheless possible to use constexpr when instantiating a struct:
rust
// allowed:
let map = Bitmap::<{64 / 8}>::new();
A bitset<N>
in C++ can be indexed by Index op []
. We have
met some problems when implementing this feature. Specifically,
implementing core::ops::Index
for a struct is like this:
rust
impl Index for T {
type Output = U;
fn index(&self, index: usize) -> &Self::Output { ... }
}
The ref in &Self::Output
requires self
to own the indexed output.
In Bitmap
, Output
is required to be "bits".
It is necessary to use a wrapper type to provide interfaces to
access a single bits. We have provided BitRef
and
BitRefMut
as the wrappers.
However, the bitmap is not expected to hold a large set of wrappers,
in order to save memories.
It is not possible either to create the wrapper in index()
and
pass it to the bitmap, since the &self
is referenced immutably.
Due to this issue, we only provide Bitmap::at()
and Bitmap::at_mut()
as methods
to index into the bitmap.
## Updates
Bitmap::any()
,
Bitmap::none()
, Bitmap::all()
,
Bitmap::count()
and Bitmap::test()
.Bitmap::find_first_one()
],
[Bitmap::find_first_zero()
].bitmap-usecase
, showing a use case of managing raw
memory resources with bitmap.0.3.0
Option
(the size of bitmap
is 1 byte bigger than the generic, which is not friendly to memory align).0.2.0
0.1.1
0.1.0