Search Results for "readme"

...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. The README shows examples: an enum with variants annotated by #[error("…")] and #[from] fields to derive the appropriate trait impls. The crate expects rustc ≥ 1.68+. The README also outlines how you choose; use thiserror if you care about designing your own error-types (e.g., for libraries) vs anyhow for applications.

Goose Swift is a local-first iOS companion project for WHOOP 5.0 devices. It is currently an alpha proof of concept intended for developers who can build the Swift app and Rust core themselves. The app connects to WHOOP 5.0 bands through Bluetooth and routes device data through a local Rust processing layer. It turns available signals into health, recovery, sleep, strain, stress, cardio, energy, coach, and debug views. The project includes a SwiftUI app, a Rust bridge, HealthKit support, a...

...The browser interface supports search, themed listings, QR codes, uploads, directory creation, deletion, and compressed folder downloads. It also handles range requests, README rendering, WebDAV, health checks, and correct MIME types. miniserve is designed for situations where starting a full web server would be unnecessary or too slow.

corroded is a Rust project that intentionally strips away Rust’s safety guarantees and idiomatic protections, offering utilities and patterns that prioritize raw power and freedom over the usual borrow checker enforcement or strict ownership rules. Its README and community reactions suggest a mix of satire and extreme experimentation: the project makes “unsafe” Rust easier to use by removing typical compile-time checks, pushing the language toward behavior more like C for cases where developers want total control. Although controversial, the code serves as an exploration of Rust internals and unsafe constructs, and it includes utilities intended to simplify memory management and pointer manipulation without safety checks. ...

This is a workshop/repository by the Rust developer David Tolnay (dtolnay) intended to teach how to write Rust procedural macros (derive macros, function-like macros, attribute macros). The repo contains multiple toy/realistic macro projects drawn from real use-cases: e.g., derive(Builder), derive(CustomDebug), seq!, #[sorted], #[bitfield]. The README indicates the focus is on learning: parsing token streams, generating code, handling generics, attribute arguments, etc. It has test harness and workflow guidance. Because procedural macros are quite subtle in Rust, this workshop is a strong resource for anyone wanting to go from beginner to intermediate/advanced macro writing.

...It supports downcasting (so you can inspect the underlying error type), and for recent versions of Rust, it will capture backtraces by default when the underlying error type doesn’t already. It also supports no_std mode (in limited form) by disabling default features. The README distinguishes it from library-oriented error crates (like thiserror): use anyhow when you just care about application-level error handling, not fine-grained types.