Below are the results of the microbenchmarks The performance of this implementation should roughly match the performance of In general, this crate will be conservative with respect to the minimum However, crate 1.y for y > 0 may require a newer minimum Rust 1.20.0, then crate 1.0.z for all values of z will also require Rustġ.20.0 or newer. The current policy is that the minimum Rust version required to use this crateĬan be increased in minor version updates. This crate's minimum supported rustc version is 1.39.0. Namely, Cargo does not yet permit optional dev dependencies. Tests are in a separate crate because of the dependency on the C++ reference To test that this library matches the output of the reference C++ library, use: $ cargo test -manifest-path test/Cargo.toml -features cpp To run tests, you'll need to explicitly run the test crate: $ cargo test -manifest-path test/Cargo.toml Library in your LD_LIBRARY_PATH (or equivalent). Note that you will need to have the C++ Snappy Tests against the reference C++ implementation can be run withĬargo test -features cpp. This seems like a reasonable starting point, although it is not necessarilyĪ goal to always maintain byte-for-byte equivalence. This crate is tested against the reference C++ implementation of Snappy.Ĭurrently, compression is byte-for-byte equivalent with the C++ implementation. It can be installed with Cargo: $ cargo install szip Szip is a tool with similar behavior as gzip, except it uses SnappyĬompression. This example can be found in examples/compress.rs: use std ::io fn main ( ) Example: the szip tool This program reads data from stdin, compresses it and emits it to stdout. DocumentationĪdd this to your Cargo.toml: snap = "1 " Example: compress data on stdin This implementation is ported from both the Includes streaming compression and decompression using the Snappy frame format.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |