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

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

#215 in #ring-buffer

Download history 470/week @ 2026-02-10 334/week @ 2026-02-17 339/week @ 2026-02-24 969/week @ 2026-03-03 1197/week @ 2026-03-10 626/week @ 2026-03-17 806/week @ 2026-03-24 733/week @ 2026-03-31 103/week @ 2026-04-07 160/week @ 2026-04-14 183/week @ 2026-04-21 176/week @ 2026-04-28 260/week @ 2026-05-05 507/week @ 2026-05-12 748/week @ 2026-05-19 559/week @ 2026-05-26

2,087 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