This package provides wrapper types and traits for secret management which help ensure they aren't accidentally copied, logged, or otherwise exposed (as much as possible), and also ensure secrets are securely wiped from memory when dropped.
Typenum is a Rust library for type-level numbers evaluated at compile time. It currently supports bits, unsigned integers, and signed integers. It also provides a type-level array of type-level numbers, but its implementation is incomplete.
This package is an implementation of parser combinators for Rust, inspired by the Haskell library Parsec. As in Parsec the parsers are LL(1) by default but they can opt-in to arbitrary lookahead using the attempt combinator.
This package is an implementation of parser combinators for Rust, inspired by the Haskell library Parsec. As in Parsec the parsers are LL(1) by default but they can opt-in to arbitrary lookahead using the attempt combinator.
This package provides a Rust implementation of fast and scalable minimal perfect hashing for massive key sets. It generates an MPHF for a collection of hashable objects.
This package provides a port of the libtest (unstable Rust) benchmark runner to Rust stable releases. Supports running benchmarks and filtering based on the name. Benchmark execution works exactly the same way and no more (caveat: black_box is still missing!).
A Multi-Cast DNS (RFC 6762) and DNS Service Discovery (RFC 6763) library. Used for resolution of hostnames to IP addresses on networks that do not have a local name server. Network services can be advertised and discovered using this mechanism.
Snapbox is a snapshot-testing toolbox that is ready to use for verifying output from
Function return values
CLI stdout/stderr
Filesystem changes
It is also flexible enough to build your own test harness like trycmd.
Snapbox is a snapshot-testing toolbox that is ready to use for verifying output from
Function return values
CLI stdout/stderr
Filesystem changes
It is also flexible enough to build your own test harness like trycmd.
Zeroize securely clears secrets from memory with a simple trait built on stable Rust primitives, which guarantee memory is zeroed using an operation will not be ``optimized away'' by the compiler. It uses a portable pure Rust implementation that works everywhere, even WASM!
Snapbox is a snapshot-testing toolbox that is ready to use for verifying output from
Function return values
CLI stdout/stderr
Filesystem changes
It is also flexible enough to build your own test harness like trycmd.
Snapbox is a snapshot-testing toolbox that is ready to use for verifying output from
Function return values
CLI stdout/stderr
Filesystem changes
It is also flexible enough to build your own test harness like trycmd.
This package provides Securely clear secrets from memory with a simple trait built on stable Rust primitives which guarantee memory is zeroed using an operation will not be optimized away by the compiler. Uses a portable pure Rust implementation that works everywhere, even WASM!
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
The windows crate lets you call any Windows API past, present, and future using code generated on the fly directly from the metadata describing the API and right into your Rust package where you can call them as if they were just another Rust module.
Clircle provides a cross-platform API to detect read or write cycles from your user-supplied arguments. You can get the important identifiers of a file (from a path) and for all three stdio streams, if they are piped from or to a file as well.