#read #structures #slice #ring-buffer #static #data-structures

wheelbuf

The wheelbuffer crate offers a ringbuffer-like structure without a read pointer, making multiple reads of a buffer possible. The store behind the buffer is flexible and can be a static array, a vector or any other structure that can be converted into a slice.

1 unstable release

Uses old Rust 2015

0.2.0 Nov 19, 2016

#132 in #ring-buffer

Download history 83/week @ 2025-07-16 87/week @ 2025-07-23 36/week @ 2025-07-30 47/week @ 2025-08-06 40/week @ 2025-08-13 88/week @ 2025-08-20 95/week @ 2025-08-27 153/week @ 2025-09-03 193/week @ 2025-09-10 111/week @ 2025-09-17 115/week @ 2025-09-24 339/week @ 2025-10-01 42/week @ 2025-10-08 113/week @ 2025-10-15 165/week @ 2025-10-22 331/week @ 2025-10-29

676 downloads per month
Used in casper-node

MIT license

7KB
170 lines

Multi-read no_std ring buffer

The wheelbuffer crate offers a ringbuffer-like structure without a read pointer, making multiple reads of a buffer possible. Instead of relying on a fixed data structure as a backend, it is generic over a type C that offers the slice interface, e.g. a vector or even a static array.

The create performs no allocations itself and does not use the standard library (#![no_std]).


Multi-read no_std ring buffer

The wheelbuffer crate offers a ringbuffer-like structure without a read pointer, making multiple reads of a buffer possible. The store behind the buffer is flexible and can be a static array, a vector or any other structure that can be converted into a slice.

Documentation is available at docs.rs.

No runtime deps