Stack Error – ergonomic error handling for Rust
Stack Error is a pragmatic error handling library for Rust that provides helpful messages for debugging, and structured data for runtime error handling. Features: * Informative error messages: stack error messages and optionally add file/line context to your messages. This helps convey not just what went wrong, but also how it went wrong, making debugging faster. * Programmatic error handling: include optional error codes and URIs for robust runtime handling. * Library-Friendly: define custom error types easily while staying compatible with Rust’s error ecosystem. If designing good…
Stack Error – ergonomic error handling for Rust launched on May 18, 2025 with 27 votes, #730 of 7,905 launches that month and more than 90% of that year's launches. The site was still online in September 2026, 1 year on.
In plain words
Stack Error is a Rust library that simplifies error handling by reducing initial design overhead. It aims to provide ergonomics comparable to anyhow while delivering informative error messages for debugging and typed data for runtime error handling. The tool is designed for Rust developers building libraries and applications who want straightforward error management without extensive upfront planning.
written from the facts on this page · September 2026
From the sources
A pragmatic error handling library for Rust that provides helpful strings for debugging, and structured data for runtime error handling. - gmcgoldr/stackerror
Stack Error reduces the up-front cost of designing an error handling solution for your project, so that you focus on writing great libraries and applications. Stack Error has three goals: Build informative error messages for debugging with minimal effort. The error message is co-located with the error source, which helps document your code. use stackerror :: prelude :: * ; pub fn process_data ( data : & str ) -> StackResult < String > { let data : Vec < String > = serde_json :: from_str ( data ) . map_err ( StackError :: from_msg ) . stack_err_msg ( fmt_loc ! ( "data is not a list of strings" ) ) ? ; data . first ( ) . cloned ( ) . ok_or_else ( StackError :: new ) . with_err_msg ( fmt_loc !…from github.com
In the maker’s words, at launch
Stack Error reduces the up-front cost of designing an error handling solution for your project, so that you focus on writing great libraries and applications. Stack Error has three goals: 1. Provide ergonomics similar to anyhow. 2. Create informative error messages that facilitate debugging. 3. Provide typed data…
Does a similar job
all alternatives →
Error return traces for Go, inspired by Zig2023 · github.com · ▲133An alternative to stack traces for your Go errors. Contribute to bracesdev/errtrace development by creating an account on GitHub.
Algorithm Cookbook in Rust2017 · github.com · ▲320Common data structures and algorithms in Rust. Contribute to EbTech/rust-algorithms development by creating an account on GitHub.
Debugging-Friendly Tracebacks for Python2019 · github.com · ▲123Debugging-friendly exceptions for Python. Contribute to cknd/stackprinter development by creating an account on GitHub.
I'm making a dynamic language in Rust2022 · github.com · ▲184An implementation of a dynamic programming language in Rust. Includes: Parser/Compiler, REPL, Virtual Machine, Bytecode Disassembler This started out as a learning project to teach myself Rust. It has grown into a decently substantial piece of software and I've learned quite a bit in the process! Some neat things: + A garbage collector that can store dynamically sized types without any double-indirection (i.e. I have my own Box implementation with manual alloc/dealloc) + The smart pointer used to reference GCed data is a thin pointer. The ptr metadata needed for DSTs is stored in…
Typed-arrow – compile‑time Arrow schemas for Rust2025 · github.com · ▲48Hi community, we just released https://github.com/tonbo-io/typed-arrow. When working with arrow-rs, we noticed that schemas are declared at runtime. This often leads to runtime errors and makes development less safe. typed-arrow takes a different approach: - Schemas are declared at compile time with Rust’s type system. - This eliminates runtime schema errors. - And introduces no runtime overhead — everything is checked and generated by the compiler. If you’ve run into Arrow runtime schema issues, and your schema is stable (not defined or switched at runtime), this project…
Cppmatch – Rust-Like Pattern Matching and Error Handling for C++2025 · github.com · ▲42I've created cppmatch, a lightweight, header-only C++ library that brings Rust-inspired pattern matching and error handling to C++. It tries to imitate the functionality of the questionmark (?) operator in C++ by using a macro that uses the gcc extension https://gcc.gnu.org/onlinedocs/gcc/Statement-Exprs.html This allows to create exceptionless code with non-intrusive error-as-value that unlike Exceptions, makes it clear which kinds of error a function can generate and forces you to handle (or ignore) them. The ? operator translates to *expect* To handle the errors I…
More dev tools this month
the category →

open-source IDE for thoughtful software design. Contribute to devdotfast/whiteboard development by creating an account on GitHub.
Dev tools · 27d ago · github.com

Contribute to reladraw/reladraw development by creating an account on GitHub.
Dev tools · 25d ago · github.com
OpenBot▲362Grok Bot alternative: free, local, open-source, multiplayer
Dev tools · 22d ago · openbot.run
Talanoa▲340Hi HN, I’m a fullstack developer, and honestly, I’ve lost count of how many side projects I’ve worked on over the years. But one idea kept coming back to me: a different kind of email client. It first came to me in 2014: “What if we could handle emails more like conversations?” Every year, I’d revisit this concept in my “Build Notes.” Ten years later, no one had built exactly what I had in mind — so I finally decided to do it myself. That’s how Talanoa was born. I wanted something focused on people, not timelines. I was tired of marking messages as unread just to remember to reply later, or…
Dev tools · 20d ago · talanoa.email
CoreSpeed▲332One MCP for everything your agents need: apps, memory, tools
Dev tools · 27d ago · corespeed.io
Source: Show HN post ↗ · launch text quoted in part
Launched alongside, May 2025
the whole month →
Tapflow 2.0▲1,125We built Tapflow for devs, designers, PMs, and tech folks who’ve been sitting on internal docs, templates, and systems — but never productized them. Upload a PDF, notes, or workshop deck, and Tapflow drafts a structured product (with chapters, teaser and pricing plans). It’s good for AI kits, onboarding guides, design systems, and frameworks. You can sell through Stripe, LemonSqueezy, or PayPal. Real-time collaboration is in early beta. No site builder, no LMS — clean design and just focused tools to ship. Fully bootstrapped and just launched on PH today →…
Work · 2025 · tapflow.ai
- C9
Life & fun · 2025 · felixrieseberg.github.io
Appwrite Sites▲990Appwrite 2.0 brings a new engine, a rebuilt Console, five database types, an S3 API, an OAuth 2.1 server, and organization-level Domains and Firewall.
Dev tools · 2025 · appwrite.io


