You claim "no dependencies", but std is actually a quite large dependency in some environments. Most of this crate can do without std and use only core (ie, function overloading traits)`.
There's a few bits which can't:
It's a bit unfortunate trying to use alloc and collections, as they are currently unstable. I recommend adding a no_std feature that explicitly depends on those crates, with internal aliases for Rc, Vec, and VecDeque that switch between std and alloc/collections based on #[cfg(feature = "no_std")]. This does imply that no_std is unstable.
If you're happy with this, I can send a PR doing these changes.
You claim "no dependencies", but std is actually a quite large dependency in some environments. Most of this crate can do without
stdand use onlycore(ie, function overloading traits)`.There's a few bits which can't:
Rchttps://github.com/RustAudio/sample/blob/4a4c679268605e539342f52b702a21189534526a/src/signal.rs#L581VecandVecDequehttps://github.com/RustAudio/sample/blob/4a4c679268605e539342f52b702a21189534526a/src/signal.rs#L590Rchttps://github.com/RustAudio/sample/blob/4a4c679268605e539342f52b702a21189534526a/src/signal.rs#L601It's a bit unfortunate trying to use
allocandcollections, as they are currently unstable. I recommend adding ano_stdfeature that explicitly depends on those crates, with internal aliases forRc,Vec, andVecDequethat switch betweenstdandalloc/collectionsbased on#[cfg(feature = "no_std")]. This does imply thatno_stdis unstable.If you're happy with this, I can send a PR doing these changes.