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!
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.
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.
The termios crate provides safe bindings for the Rust programming language to the terminal I/O interface implemented by Unix operating systems. The safe bindings are a small wrapper around the raw C functions, which converts integer return values to std::io::Result to indicate success or failure.
This crate contains what aims to be the simplest possible implementation of a valid executor. Instead of nicely parking the thread and waiting for the future to wake it up, it continuously polls the future until the future is ready. This will probably use a lot of CPU, so be careful when you use it.
Juniper makes it possible to write GraphQL servers in Rust that are type-safe and fast. It also tries to make declaring and resolving GraphQL schemas convenient.
Juniper does not include a web server. Instead it provides building blocks to make integration with existing servers straightforward. It optionally provides a pre-built integration for the Actix, Hyper, Iron, Rocket, and Warp frameworks, including embedded Graphiql and GraphQL Playground for easy debugging.
Juniper makes it possible to write GraphQL servers in Rust that are type-safe and fast. It also tries to make declaring and resolving GraphQL schemas convenient.
Juniper does not include a web server. Instead it provides building blocks to make integration with existing servers straightforward. It optionally provides a pre-built integration for the Actix, Hyper, Iron, Rocket, and Warp frameworks, including embedded Graphiql and GraphQL Playground for easy debugging.
Rustic is a fork of Rust mode. In addition to its predecessor, it offers the following features:
Flycheck integration,
Cargo popup,
multiline error parsing,
translation of ANSI control sequences through XTerm color,
asynchronous Org Babel,
custom compilation process,
rustfmterrors in a Rust compilation mode,automatic LSP configuration with Eglot or LSP mode,
optional Rust inline documentation,
etc.
EdDSA over Curve25519 is specified in RFC 8032. This package contains an ed25519::Signature type which other packages can use in conjunction with the signature::Signer and signature::Verifier traits. It doesn't contain an implementation of Ed25519.
These traits allow packages which produce and consume Ed25519 signatures to be written abstractly in such a way that different signer/verifier providers can be plugged in, enabling support for using different Ed25519 implementations, including HSMs or Cloud KMS services.
EdDSA over Curve25519 is specified in RFC 8032. This package contains an ed25519::Signature type which other packages can use in conjunction with the signature::Signer and signature::Verifier traits. It doesn't contain an implementation of Ed25519.
These traits allow packages which produce and consume Ed25519 signatures to be written abstractly in such a way that different signer/verifier providers can be plugged in, enabling support for using different Ed25519 implementations, including HSMs or Cloud KMS services.
An Ini configuration file parsing library in Rust
This package provides An Ini configuration file parsing library in Rust.