I need smoltcp
's RingBuffer
for a non-networking project and would like to see it in a dedicated library. I don't want to include the smoltcp
dependency for that, because it always expects at least one networking feature to be enabled and can't be used with default-features = "false"
.
I also cannot use heapless::Deque
, because I want to pass a mutable slice to the underlying buffer instead of creating a ring buffer type with a fixed size as part of its type parameters.
Would you accept a PR that moves RingBuffer
into its own library?
Any preferences where the new RingBuffer
crate should live?