Crates.io | rle-decode-fast |
lib.rs | rle-decode-fast |
version | 1.0.3 |
source | src |
created_at | 2019-06-30 14:01:50.454 |
updated_at | 2022-01-30 22:56:56.002573 |
description | Deprecated: this is available in stable Rust since 1.53 as Vec::extend_from_within(). Previsouly, the fastest way to implement any kind of decoding for Run Length Encoded data in Rust. |
homepage | |
repository | https://github.com/WanzenBug/rle-decode-helper |
max_upload_size | |
id | 144978 |
size | 84,587 |
The same functionallity is available in stable Rust since 1.53, use that instead
THE fastest way to implement any kind of decoding for Run Length Encoded data in Rust.
Writing a fast decoder that is also safe can be quite challenging, so this crate is here to save you the hassle of maintaining and testing your own implementation.
Of course, you need to depend on this crate:
rle-decode-fast = "1.0"
There is only a single function to use, rle_decode<T>(&mut Vec<T>, lookbehind_size: usize, fill_length: usize)
.
It takes :
vector[(vector.len() - lookbehind)..])
fill_length
items.use rle_decode_fast::rle_decode;
let mut decode_buffer = vec![0, 0, 1, 1, 0, 2, 3];
let lookbehind_length = 4;
let output_length = 10;
rle_decode(&mut decode_buffer, lookbehind_length, output_length);
assert_eq!(decode_buffer, [0, 0, 1, 1, 0, 2, 3, 1, 0, 2, 3, 1, 0, 2, 3, 1, 0]);
There are cases where the decode functions panics
The idea for this crate first originated from this pre-RFC. It brought to attention a weak-point in the standard library, which lead some crates writing their own unsafe by-pass.
During the exploration happening in the pre-RFC, some experimentation was conducted. For examples see here and here.
There is a benchmark comparing a naive (repeated push) implementation, a vulnerable implementation that might lead to uninitialized memory and this crate.
The results for a very small fill length and for a bigger fill lengths
Licensed under either of
at your option.
Unless you explicitly state otherwise, any contribution intentionally submitted for inclusion in the work by you, as defined in the Apache-2.0 license, shall be dual licensed as above, without any additional terms or conditions.