Ergonomic errors in Rust: write fast, debug with ease, handle precisely

https://gmcgoldr.github.io/2025/08/21/stackerror.html

17•garrinm•1d ago

Comments

TheCleric•5h ago

This just feels like recreating exceptions, but with more complicated syntax.

XorNot•5h ago

I mean broadly that's my entire problem with errors as values: every implementation wastes a ton of syntax trying to make them like exceptions.

MindSpunk•3h ago

The common problems with exceptions isn’t the easy part of try/catch, it’s the execution model and “any function could throw” that causes most contention. Error values are logically simpler and fully document if and what errors the function can return. Checked exceptions solve that too, but in practice nobody used them even where available. And you still end up with hidden control flow with exceptions, the exceptional path through a function is syntactically invisible and difficult to audit without very strong language tooling.

marcianx•1h ago

And also the issue with checked exceptions is that one can't be generic over the checked exception, at least in Java. So it's impossible to write out a universally useful function type that's strictly typed on the error. This definition of `ThrowingFunction` for Java [1] needs just have `throws Exception`, allowing just about anything to be thrown.

Most functional-inspired languages would just have a single `f: T -> Result<U, E>` interface, which supports both (1) a specific error type `E`, which can also be an uninhabited type (e.g. never type) for an infallible operation, and (2) where `U` can be the unit type if the function doesn't return anything on success. That's about as generic as one can get with a single "interface" type.

[1]: https://docs.spring.io/spring-framework/docs/current/javadoc...

catlifeonmars•1h ago

Sometimes it’s nice to have one control flow mechanism rather than too. One could argue that traditional exceptions are more complicated with a their alternative control flow and syntax.

adastra22•5h ago

How is this different from the even more ergonomic “#[from]” provided by thiserror?

echelon•4h ago

Are all of these proc macros worth it? The compile times for proc macros explode.

I'd rather hand-roll errors than deal with more proc macros. Or better yet, have code gen pay the cost once and never deal with it again.

alfiedotwtf•4h ago

Cognitive load is more expensive than compilation time.

echelon•4h ago

Compilation time turns into cognitive load via frustration. Death by a thousand cuts.

adastra22•3h ago

How long are your compiles? The longest I’ve ever seen is a massive Bevy project with 700 dependencies, and it still compiled in <5min from an empty cache, and then 2-3 second incremental builds (mostly link time).

dijksterhuis•3h ago

https://xkcd.com/303/

(compilation time is good for brain switch off time - i.e. reducing cognitive load).

echelon•54m ago

I find it's great for letting ADHD take over steering the ship and losing total focus on what needs to be done.

Which is more or less what this XKCD encapsulates.

duped•2h ago

Frankly, std::io:Error::other is good enough most of the time.

Spooky_Fusion1•4h ago

Thankyou for pointing out a Rust, crate, error handler. Judging by the other comments, it's just as well you did,as I will look more closely at its use with virtual DOM. Thankyou.

QuaternionsBhop•4h ago

I have never seen anything use Result<_,&'static str>, that is such an anti-rust thing to start with.

adastra22•3h ago

LLMs love to do this. I assume they are trying to write JavaScript or Python or whatever, but in Rust.

I have never seen an actual Rist programmer do this, and that was clue #1 that TFA was AI generated without review.

bigstrat2003•2h ago

I do when prototyping. Long term you don't really want to pass around &str errors, but they are quick and dirty and easy to get rolling with.

adastra22•1h ago

Seems just as quick to make an enum with thiserror string conversion? Not much boilerplate at least.

hardwaresofton•3h ago

OP should really mention that they made stackerror. I couldn’t shake the feeling that this read like an ad for stackerror… and of course the author is the crate writer. This feels somewhat disingenuous without a disclaimer that you wrote the lib and there are other ways.

The general advice is good (except for the awkward use of std error), so for anyone who wants to know what rustaceans are actually using:

- std error when it’s required

- anyhow for flexibly dealing with large classes of errors and rethrowing (often in bin crates or internally in a lib crate ), use anyhow::Context to tag errors

- thiserror for building and generating custom errors (in a lib crate)

- miette/eyre for more advanced features

Watch out for exposing error types in public API because then you are bound to push a breaking change if the upstream does.

Anyhow will probably never have a v2 at this point IMO, the entire Rust ecosystem might have to rev!

[EDIT] dont want to suggest that people avoid stackerror, just want to show what other ecosystem projects there are! stackerror seems to fit the hole of anyhow.

faangguyindia•2h ago

Rust used to be pretty hard to read and write, now with ai coding agent not anymore.

Analemma_•1h ago

Have you had success doing non-trivial Rust with AI agents? In my experience they're all pretty bad at it once you get beyond the basics and start having tricky lifetimes and complicated types, but I'm interested to hear what people have done to make it better.

AGI is an engineering problem, not a model training problem

The cost of interrupted work (2023)

I built a tiny mac app to monitor and manage my development processes

Show HN: How to Build a Coding Agent (free workshop)

Line scan camera image processing for train photography

How can AI ID a cat?

What makes Claude Code so damn good

A 2k-year-old sun hat worn by a Roman soldier in Egypt

Agentic Browser Security: Indirect Prompt Injection in Perplexity Comet

Static sites with Python, uv, Caddy, and Docker

Evaluating LLMs for my personal use case

Physics of badminton's new killer spin serve

Librebox: An open source, Roblox-compatible game engine

Taking a look at my old Palm IIIx – by Paul Lefebvre

Acronis True Image costs performance when not used

RFC 9839 and Bad Unicode

Texas Instruments’ new plants where Apple will make iPhone chips

Motion (YC W20) Is Hiring Principal Software Engineers

Why was Apache Kafka created?

Debdelta

DeepCode: Open Agentic Coding

Romhack.ing's Internet Archive Mirror No Longer Available

Hacker and physicist – a tale of "common sense"

Not so prompt: Prompt optimization as model selection (2024)

The Cornervery: A 90-Degree Stapler

Writing Speed-of-Light Flash Attention for 5090 in CUDA C++

Libre – An anonymous social experiment without likes, followers, or ads

Monoid-Augmented FIFOs, Deamortised

Optimizing our way through Metroid

Exploring EXIF (2023)