Search Results for "std"
Sort By:
Showing 8 open source projects for "std"
View related business solutions-
$300 Free Credits to Build on Google CloudPut your $300 in credit toward real workloads, then keep building with free monthly usage for 20+ products. No commitment and no charge until you upgrade.
-
99.99% Uptime for MySQL and PostgreSQL DatabasesCloud SQL Enterprise Plus delivers near-zero downtime with 35 days of point-in-time recovery. Supports MySQL, PostgreSQL, and SQL Server.
-
1
async-std
Async version of the Rust standard library
async-std makes async programming foundations easy and approachable. Built-in Rust for speed and safety. -
2
ntex
framework for composable networking services
Framework for composable network services. Starting ntex v0.5 async runtime must be selected as a feature. Available options are glommio, tokio or async-std. -
3
derive(Error)
derive(Error) for struct and enum error types
This is a Rust crate that provides a convenient derive macro (#[derive(Error)]) for implementing std::error::Error on your custom error types (structs or enums). The goal is to enable library authors to build expressive, typed error types, with readable Display implementations (via #[error("...")] annotations) as well as From conversions (#[from]), source tracking (#[source]), and optionally backtraces. It is designed so that switching from handwritten error implementation to using this error is not a breaking change: you retain the same API. ... -
4
Anyhow
Flexible concrete Error type built on std::error::Error
This is a Rust library (crate) that provides a flexible, concrete error type built atop the standard std::error::Error trait. Its primary goal is to make error handling in applications easy: instead of defining lots of custom error types, you can use anyhow::Error (or the alias anyhow::Result<T>) for fallible functions. The crate supports attaching context to errors, so you can convert a low-level error (like “file not found”) into one with richer diagnostics (“Failed to read instructions from path X”) using .context() or .with_context(). ... -
Cut Data Warehouse Costs by 54%BigQuery delivers 54% lower TCO with exabyte scale and flexible pricing. Free migration tools handle the SQL translation automatically.
-
5
mlua
High level Lua 5.4/5.3/5.2/5.1 and Roblox Luau bindings to Rust
mlua is binding to Lua programming language for Rust with a goal to provide safe (as far as it's possible), high-level, easy-to-use, practical, and flexible API. Started as rlua fork, mlua supports Lua 5.4, 5.3, 5.2, 5.1 (including LuaJIT) and Roblox Luau and allows to writing of native Lua modules in Rust as well as the use of Lua in a standalone mode. mlua tested on Windows/macOS/Linux including module mode in GitHub Actions on x86_64 platform and cross-compilation to aarch64 (other... -
6
DashMap
Blazing fast concurrent HashMap for Rust
Blazingly fast concurrent map in Rust. DashMap is an implementation of a concurrent associative array/hashmap in Rust. DashMap tries to implement an easy-to-use API similar to std::collections::HashMap with some slight changes to handle concurrency. DashMap tries to be very simple to use and to be a direct replacement for RwLock<HashMap<K, V>>. To accomplish these goals, all methods take &self instead of modifying methods taking &mut self. This allows you to put a DashMap in an Arc<T> and share it between threads while still being able to modify it. ... -
7
Zerocopy
Zerocopy makes zero-cost memory manipulation effortless
Zerocopy is a Rust library designed to make zero-cost memory manipulation both safe and effortless. It allows developers to reinterpret or convert raw byte sequences into structured types—and vice versa—without writing unsafe code directly. The crate provides safe abstractions for transmuting data while preserving Rust’s strict safety guarantees, removing the need for manual memory manipulation. Zerocopy introduces a suite of conversion traits such as TryFromBytes, FromBytes, IntoBytes, and... -
8
rust_cmd_lib
Common rust command-line macros and utilities
...The library also supports features like variable substitution, scoped environment settings, and defining custom commands (functions) that behave like built-ins. It hides much of the boilerplate of std::process::Command when you're doing simple task automations, but still allows full flexibility when needed. Because it avoids launching a shell, it reduces some classes of security and quoting errors, while improving readability of scripting logic inside a Rust binary.
- Previous
- You're on page 1
- Next
