HN Reader

I think I reach the opposite conclusion which is that I'd not take a library dependency to get the non-growable version. I would however like push_within_capacity (currently available on Vec in nightly) so that I can express the idea "I would prefer to push this into the ring buffer but I have some plan B if there's no room"

Since we're talking about ring buffers, here's one awesome crate I've used quite a few times - https://github.com/hawkw/thingbuf (concurrent lock-free ring buffer)

I've used these in rust to record and play audio on embedded devices. The gist is, you set up a static mut array, set the DMA peripheral to write or read to it and circular mode. Use indexes to split the buffer in the middle; you do CPU IO on the half the DMA isn't accessing. Use a Half-Transfer interrupt to trigger these CPU reads/writes.

In my work, we had to use a ring buffer to play audio data (we decode audio data to raw WAV and use a ring buffer for playback).

Interestingly, while the core part of the audio process is in rust (through WASM), the ring buffer itself is written in JS land (shared array buffer so that the audio context can read from it).

for some reason, i always had problems with the concept of ring buffers - because what happens if end wraps around and overtakes start?

it always takes me a few seconds (well, more than a few actually) to work out that in that case, the buffer is just full (like every other buffer).