Anyhow

Right, so you’ve got your error all boxed up in an anyhow::Error. It’s wonderfully convenient, but now you need to actually do something with it. You can’t just shrug and say “something went wrong” to the user; you need to tell them their database connection string was malformed, or that the configuration file is missing a required section. This is where we go from error handling to error interrogation. We need to crack that anyhow::Error open to see what’s inside. The process is called downcasting.

Alright, let’s cut through the noise. You’ve got errors, and you’ve got two fantastic tools to deal with them: thiserror and anyhow. Using them effectively isn’t about which one is “better”—it’s about using the right tool for the job. And the job is defined by what you’re building: a reusable library or a final application binary. Get this wrong, and you’ll annoy other developers (if you’re writing a library) or drown in your own frustration (if you’re writing a binary).

Alright, let’s talk about anyhow. If thiserror is your meticulous, type-safe blueprint for building known errors, anyhow is the duct tape, WD-40, and the “I’ll deal with that later” box you use when you’re actually running your application. Its entire reason for existence is to make error handling in applications, not libraries, ridiculously ergonomic. The core problem in application code is often this: you’re calling ten different functions from seven different libraries, each returning their own bespoke enum error type. You don’t really care about the specific variant in your main(); you mostly just want to know something went wrong and print a decent message for the user (or for your logs). Manually converting all those errors into your own type with From is a chore that adds zero value. Enter anyhow.

Now, let’s get to the good stuff: writing custom error types by hand is a fantastic way to build character and appreciate the finer points of the std::error::Error trait. It’s also tedious, error-prone, and frankly, a bit of a drag. You’re a busy person. You have bugs to write—I mean, fix. Enter thiserror, the crate that does the boring, mechanical work for you, letting you focus on the actual design of your errors.

Alright, let’s talk about the source() method. This is the secret handshake of the Rust error ecosystem, the mechanism that lets one error politely point to the cause of another, forming a chain of blame that you can follow all the way back to the root cause. It’s how we get those beautiful, multi-line error reports that actually tell you what went wrong instead of just coyly shrugging. Think of it like this: you ask your friend why the party was cancelled. They say, “The venue flooded.” That’s the error. The source() method is you asking, “Why was it flooded?”, and your friend replying, “A pipe burst.” That’s the source. You can keep asking “why?” until you get to the root cause, which is probably some contractor in the 80s using the wrong kind of pipe. The std::error::Error trait’s source() method formalizes this “why?” question.

Alright, let’s talk about giving your custom errors a face. You’ve defined a nice, structured enum (or struct) to represent all the ways your code can politely explode. But right now, if you try to print it with println!("{}", my_error), Rust will stop you cold. It’s like having a brilliant thesis but no way to present it. The Display trait is your podium. Rust’s error handling is built on the std::error::Error trait, and that trait requires that your type also implement Display. Why? Because at the end of the day, someone needs to see what went wrong, whether it’s a user in a CLI or you, debugging at 2 AM. The Display trait is how you translate your internal, structured error into a human-readable message. It’s the UX layer for your failures.

Alright, let’s roll up our sleeves and get our hands dirty with manual Error trait implementation. You might be asking, “Why would I ever do this when thiserror exists?” Fair question. Think of it like this: using thiserror is like having a brilliant assistant who writes your reports. Implementing it manually is you staying up all night, coffee-stained and muttering, to truly understand how the report is structured. You do it once to know what the assistant is actually doing for you. It makes you a better debugger and a more conscious programmer. Plus, sometimes you need to do something so weird that even thiserror can’t help you.