Would `smoltcp` accept a PR that moves `RingBuffer` into a dedicated library?

[ColinFinck]

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?

[Dirbaio]

The goal of the smoltcp project is to produce a network stack. Splitting the ringbuffer into a separate lib would require effort to document it, changelog it, design the public API, then people will file PRs and issues against it to make it work for their use cases that are beyond what smoltcp needs.

So IMO it's out of scope. Feel free to copy-paste it though, it's open-source after all.