generic-vec
A vector that can store items anywhere: in slices, arrays, or the heap!
GenericVec has complete parity with Vec, and even provides some features
that are only in nightly on std (like GenericVec::drain_filter), or a more permissive
interface like GenericVec::retain. In fact, you can trivially convert a Vec to a
HeapVec and back!
This crate is no_std compatible.
Features
std(default) - enables you to use an allocator, andalloc- enables you to use an allocator, for heap allocated storages (likeVec)nightly- enables you to use array (T; N) based storages
Basic Usage
On stable no_std you have two choices on for which storage you can use
SliceVec or InitSliceVec. There are three major differences between
them.
- You can pass an uninitialized buffer to
SliceVec - You can only use
Copytypes withInitSliceVec - You can freely set the length of the
InitSliceVecas long as you stay within it's capacity
use ;
let mut uninit_buffer = uninit_array!;
let mut slice_vec = new;
assert!;
slice_vec.push;
assert_eq!;
let mut init_buffer = 0xae; 16;
let mut slice_vec = new;
assert!;
assert_eq!;
slice_vec.set_len;
assert!;
Of course if you try to push past a *SliceVec's capacity
(the length of the slice you passed in), then it will panic.
let mut init_buffer = 0xae; 16;
let mut slice_vec = new;
slice_vec.push;
If you enable the nightly feature then you gain access to
ArrayVec and InitArrayVec. These are just like the
slice versions, but since they own their data, they can be
freely moved around, unconstrained. You can also create
a new ArrayVec without passing in an existing buffer.
use ArrayVec;
let mut array_vec = new;
array_vec.push;
array_vec.push;
array_vec.push;
assert_eq!;
The ditinction between ArrayVec and InitArrayVec
is identical to their slice counterparts.
Finally a HeapVec is just Vec, but built atop GenericVec,
meaning you get all the features of GenericVec for free! But this
requries either the alloc or std feature to be enabled.
Current version: 0.1.0-alpha
License: MIT/Apache License 2.0