EXExpurple·Jun 3, 2025
Thiserror 2.0 (released 6 months ago) supports no_std.
https://github.com/dtolnay/thiserror/releases/tag/2.0.0
In Why Use Structured Errors in Rust Applications?dtolnay
thiserror
Rust2020–2025
dtolnay / thiserror
thiserror
derive(Error) for struct and enum error types
10Distinct people
10Mentions
0Explicit recommenders
5.6KGitHub stars
What to know before exploring
What it is
derive(Error) for struct and enum error types
GitHub
Where it is used
No documented product use has been verified yet.
What people are saying
No recommendation phrase was found in the indexed comments.
No classified warning is attached to this page. Read the discussions before treating silence as approval.
Also in these discussions
- dtolnay/anyhow · linked in 4 of the same discussions
Mentioned in the same Hacker News threads. That is not proof they are substitutes.
This week on Hacker News
Nov 8–Nov 15 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/15/2026, 2:04:58 PM UTC.
No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.
Mentions over time
HN mentions by year10 dated mentions
Observed mentions: 2020-04-23 17:37:49 UTC to 2025-06-03 13:39:29 UTC.
Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.
View mention counts and date ranges
| Period | Start (UTC) | End (exclusive, UTC) | Mentions | Submissions | Comments |
|---|---|---|---|---|---|
| 2020 | 2020-01-01 00:00:00 UTC | 2021-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2021 | 2021-01-01 00:00:00 UTC | 2022-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2022 | 2022-01-01 00:00:00 UTC | 2023-01-01 00:00:00 UTC | 2 | 0 | 2 |
| 2023 | 2023-01-01 00:00:00 UTC | 2024-01-01 00:00:00 UTC | 0 | 0 | 0 |
| 2024 | 2024-01-01 00:00:00 UTC | 2025-01-01 00:00:00 UTC | 4 | 0 | 4 |
| 2025 | 2025-01-01 00:00:00 UTC | 2026-01-01 00:00:00 UTC | 2 | 0 | 2 |
What Hacker News says
10 sourcesPretty surprised not to see SNAFU [1] on that list. Very comfortable to use, kind of a mix of thiserror [2] and anyhow [3] I think.
[1] https://github.com/shepmaster/snafu
[2] https://github.com/dtolnay/thiserror
[3] https://github.com/dtolnay/anyhow
In Show HN: Cot: a Rust web framework for lazy developersInspired by this blog post I just added an `#[implicit]` field feature to the `thiserror` crate. It makes it easy to automatically annotate errors with things like code location (per this blog post), a timestamp, or a backtrace without requiring further modifications to the thiserror crate. I'm hoping that dtolnay will consider it. You can find my PR here: https://github.com/dtolnay/thiserror/pull/402
In Error Stacking in RustIt's technically feasible to add SpanTrace support to thiserror fairly easily (30 mins work - Issue: https://github.com/dtolnay/thiserror/issues/400, PR: https://github.com/dtolnay/thiserror/pull/401). This would solve part of the problem in a way that is meaningfully good for that side of the ecosystem. I suspect you could probably do something similar for Snafu
In Error Stacking in RustHere’s an example of a common Rust dependency which had a very subtle caching issue: https://github.com/dtolnay/thiserror/pull/279
In HPy – A better C API for PythonThat was a pleasure to read. Well written, nicely formatted and good links to further reading topics.
The only missing piece was talking about https://github.com/dtolnay/thiserror which I would expect to be prominently featured given how prevalent it is
And possibly https://github.com/dtolnay/anyhow which is arguably a simpler form of "error handling" but sometimes that's all you need—although probably not in the Finance or Space industries ;-)
In Guide to Error Handling in RustI dont think you realize how ridiculous this comment is. Youre comparing 10 lines of Go, with 200 of Rust:
https://github.com/dtolnay/thiserror/blob/master/src/lib.rs
In Generics can make your Go code slower> have you ever actually done that? I have, its not easy.
Yes. I do it frequently. "#[derive(Error, Debug)]": https://github.com/dtolnay/thiserror#example
Much easier than implementing the error interface in go.
Rust is powerful enough to allow macros to remove annoying boiler-plate, and so most people using rust will grab one of the error-handling crates that are de-facto standard and remove the minor pain you're talking about.
In go, it's not really possible to do this because the language doesn't provide such macros (i.e. the old third-party github.com/pkg/errors wanted you to implement 'Cause', but couldn't provide sugar like 'this-error' does for it because go is simply less powerful).
I've found implementing errors in go to be much more error-prone and painful than in rust, and that's not to mention every function returning untyped
Read the rest
errors, meaning I have no clue what callers should check for and handle new errors I add.
> The type of error objects is still a mess. Rust needs something like Python's exception type hierarchy and a consistent way to convert special error types into more general ones. I notice there's a Rust working group on error handling, again.
Anyhow[1] and thiserror[2] really help here, no?
1. https://github.com/dtolnay/anyhow
2. https://github.com/dtolnay/thiserror
In Why Rust Is the Future of Game DevelopmentTo clarify for others: "anyhow" and "thiserror" are not placeholder names in that sentence. They refer to:
https://github.com/dtolnay/anyhow
https://github.com/dtolnay/thiserror
In Rust 1.43