Crates.io | append-only-bytes |
lib.rs | append-only-bytes |
version | 0.1.12 |
source | src |
created_at | 2022-12-06 03:45:14.901732 |
updated_at | 2023-10-28 05:34:22.17669 |
description | Shareable append-only bytes |
homepage | https://github.com/zxch3n/append-only-bytes |
repository | https://github.com/zxch3n/append-only-bytes |
max_upload_size | |
id | 730826 |
size | 19,371 |
append-only-bytes
If an array is append-only and guarantees that all the existing data is immutable, we can safely share slices of this array across threads, while the owner can still safely append new data to it.
This is safe because no mutable byte has more than one owner. If there isn't enough capacity for a new append, AppendOnlyBytes
will not deallocate the old memory if a ByteSlice
is referring to it. The old memory will be deallocated only when all the ByteSlice
s referring to it are dropped.
use append_only_bytes::{AppendOnlyBytes, BytesSlice};
let mut bytes = AppendOnlyBytes::new();
bytes.push_slice(&[1, 2, 3]);
let slice: BytesSlice = bytes.slice(1..);
bytes.push_slice(&[4, 5, 6]);
assert_eq!(&*slice, &[2, 3]);
assert_eq!(bytes.as_bytes(), &[1, 2, 3, 4, 5, 6])
serde
: support serde serialization and deserializationu32_range
: support u32
range for ByteSlices
method