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.

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.