starb.git/src, branch next rust library for statically allocated ring buffers https://git.spork.org/starb.git/atom?h=next 2022-10-12T16:45:43Z remove extra semicolon 2022-10-12T16:45:43Z Brian Cully bjc@kublai.com 2022-10-12T16:45:43Z urn:sha1:8d01ca0561ec877fb24fb47eb6ddc37e5c2a0bc0 Fix clippy lints. 2019-09-09T22:20:00Z Brian Cully bjc@kublai.com 2019-09-09T22:20:00Z urn:sha1:8ee3e7b59c3531b9a79758d29ef9fde8c4790e58 Remove calls to mem::transumte. 2019-09-09T22:18:59Z Brian Cully bjc@kublai.com 2019-09-09T22:18:59Z urn:sha1:e75ed40e73586479334649dc17f46a7fd8409756 I was under the mistaken impression that mutable `AtomicUsize` was needed, when it's not. Simplify all code to use normal borrows instead of pointers with transmute. Remove `Sync` marker for Reader/Writer. 2019-09-02T15:42:29Z Brian Cully bjc@kublai.com 2019-08-15T19:04:07Z urn:sha1:0654e10d0078955d6917db504ee5947846d4f952 These are not sync, as they can only be used from one thread at a time. Also add a `Send` trait for `RingBuffer`, as long as its element type is also `Send`. Finish documentation sentence for `unshift_from`. 2019-08-14T22:26:01Z Brian Cully bjc@kublai.com 2019-08-14T22:26:01Z urn:sha1:7f3dcf01dedd39d33009e53227162012f4473dce Remove un-needed feature gate. 2019-08-14T21:50:15Z Brian Cully bjc@kublai.com 2019-08-14T21:50:15Z urn:sha1:3f23bd3113c99cfddedfa6921db2bab5ddccb6de This should work on stable now. Relax ordering and use fences where necessary. 2019-08-14T21:31:30Z Brian Cully bjc@kublai.com 2019-08-14T21:31:30Z urn:sha1:4897846bcde744ef6cfcad38fd45fe0321613f44 Remove `Copy` requirement for most methods. 2019-08-14T20:41:59Z Brian Cully bjc@kublai.com 2019-08-14T20:41:59Z urn:sha1:234ac98e16d1c05322a22e5ad1b293cbb04d864d The ring buffer will now take and pass ownership as required, so the `Copy` trait constraint is no longer required. The one exception is `Writer::unshift_from`, where we're taking data we don't know how to replace from an arbitrary slice, so that needs to be `Copy`-able. API Change: Don't require default value for RingBuffer::new(). 2019-08-14T20:10:27Z Brian Cully bjc@kublai.com 2019-08-14T20:10:27Z urn:sha1:46c82747f50aa3e77e33888de56101c8a40bda5c Use mem::MaybeUninit as the backing store so initialization is no longer required in `new`. This is safe, because you can't read anything out of the ring buffer until you store something, which initializes the memory. Add Writer::unshift_from for batch copying data in. 2019-08-14T00:11:57Z Brian Cully bjc@kublai.com 2019-08-14T00:03:11Z urn:sha1:8647cf58a27e56c9fd978c7340ee74c95fbec01f This is just the inverse of Reader::shift and exists for the same reasons.