Crates.io | recycle_vec |
lib.rs | recycle_vec |
version | 1.1.2 |
source | src |
created_at | 2019-10-31 09:32:40.488323 |
updated_at | 2024-10-28 18:22:02.223338 |
description | Provides a method for Vec to recycle it's backing allocation for use with another Vec of different type. |
homepage | |
repository | https://github.com/golddranks/recycle_vec |
max_upload_size | |
id | 177116 |
size | 13,509 |
Note: There used to be an RFC for making this functionality a part of the standard library. However, it was closed because 1) an additional API as little as this doesn't need a full RFC anymore 2) but the capabilities of the language around checking invariants statically aren't there yet, so the API would be suboptimal and therefore it's best to wait for the const generics and static checking stuff to catch up.
This crate provides a recycle
extension method for Vec
.
It's intended to change the type of the Vec
while "recycling"
the underlying allocation. This is a trick that is useful especially
when storing data with short lifetimes in Vec
:
let mut objects: Vec<Object<'static>> = Vec::new();
while let Some(byte_chunk) = stream.next() { // byte_chunk only lives this scope
let mut objects_temp: Vec<Object<'_>> = objects.recycle();
// Zero-copy parsing; Object has references to chunk
deserialize(byte_chunk, &mut objects_temp)?;
process(&objects_temp)?;
objects = objects_temp.recycle();
} // byte_chunk lifetime ends
This crate uses internally unsafe
to achieve it's functionality.
However, it provides a safe interface. To achieve safety, it does
the following precautions:
Vec
to zero length, dropping all the values.
This ensures that no values of arbitrary types are transmuted
accidentally.Vec
is compatible layout-wise. The sizes and alignments are checked
statically, so if the compile will fail in case of a mismatch.Vec
value using from_raw_parts
instead of
transmuting, an operation whose soundness would be questionable.