This crate lets you write system dependencies in Cargo.toml metadata, rather than programmatically in build.rs. This makes those dependencies declarative, so other tools can read them as well.
This package provides FFI bindings to the various libwayland-*.so libraries. You should only need this crate if you are working on custom wayland protocol extensions. Look at the crate wayland-client for usable bindings.
This crate provides bindings for OpenGL/Vulkan support for Wayland client apps. It creates an EGLSurface from any WlSurface, which can then play the role of the base surface for initializing an OpenGL or Vulkan context.
This crate provides bindings for OpenGL/Vulkan support for Wayland client apps. It creates an EGLSurface from any WlSurface, which can then play the role of the base surface for initializing an OpenGL or Vulkan context.
This package provides FFI bindings to the various libwayland-*.so libraries. You should only need this crate if you are working on custom Wayland protocol extensions. Look at the crate rust-wayland-client for usable bindings.
This package provides FFI bindings to the various libwayland-*.so libraries. You should only need this crate if you are working on custom Wayland protocol extensions. Look at the crate rust-wayland-client for usable bindings.
This package provides FFI bindings to the various libwayland-*.so libraries. You should only need this crate if you are working on custom Wayland protocol extensions. Look at the crate rust-wayland-client for usable bindings.
This package provides FFI bindings to the various libwayland-*.so libraries. You should only need this crate if you are working on custom Wayland protocol extensions. Look at the crate rust-wayland-client for usable bindings.
This package provides FFI bindings to the various libwayland-*.so libraries. You should only need this crate if you are working on custom Wayland protocol extensions. Look at the crate rust-wayland-client for usable bindings.
This package provides FFI bindings to the various libwayland-*.so libraries. You should only need this crate if you are working on custom Wayland protocol extensions. Look at the crate rust-wayland-client for usable bindings.
This package provides FFI bindings to the various libwayland-*.so libraries. You should only need this crate if you are working on custom Wayland protocol extensions. Look at the crate rust-wayland-client for usable bindings.
MagicCrypt is a library to encrypt/decrypt strings, files, or data, using Data Encryption Standard(DES) or Advanced Encryption Standard(AES) algorithms. It supports CBC block cipher mode, PKCS5 padding and 64, 128, 192 or 256-bits key length.
The central type in Apache Arrow are arrays, which are a known-length sequence of values all having the same type. This crate provides concrete implementations of each type, as well as an Array trait that can be used for type-erasure.
The central type in Apache Arrow are arrays, which are a known-length sequence of values all having the same type. This crate provides concrete implementations of each type, as well as an Array trait that can be used for type-erasure.
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.
This package is a Rust library for compiling and matching regular expressions. It uses a hybrid regex implementation designed to support a relatively rich set of features. In particular, it uses backtracking to implement features such as look-around and backtracking, which are not supported in purely NFA-based implementations.
This package is a Rust library for compiling and matching regular expressions. It uses a hybrid regex implementation designed to support a relatively rich set of features. In particular, it uses backtracking to implement features such as look-around and backtracking, which are not supported in purely NFA-based implementations.