wherror
The same derive(Error) macro thiserror provides + the features you want!
wherror = thiserror + WHERE your errors occurred π―
Why Choose wherror Over thiserror?
wherror implements the most requested community features:
| Feature | wherror | thiserror | Community Interest |
|---|---|---|---|
| Drop-in replacement for existing code | β | β | Zero migration effort |
Automatically use Debug as Display with #[error(debug)] |
β | β | #172 - not planned! |
| Call-site location tracking | β | β | #142 - 17π since 2021 |
Enhanced ergonomics (Box<T> unwrapping, .location() method) |
β | β | wherror enhancements |
Use wherror when you need these features today, with the same reliable API you know and love.
See the CHANGELOG
[]
= "2"
π― Instant Error Location Tracking
Know exactly where your errors originated with zero boilerplate:
use Error;
// Location automatically captured when using `?` - no manual work required!
π Debug Fallback - No More Boilerplate Messages
Sometimes your enum variant names are the error message. wherror lets you skip
the redundant #[error("...")] attributes that thiserror forces you to write:
use Error;
// π Fallback for variants without explicit messages
Example: All Features in Action
use Error;
// β¨ Fallback for variants without explicit messages
Quick Migration from thiserror
Step 1: Update your Cargo.toml:
[]
# thiserror = "2" # Replace this
= "2" # With this
Step 2: Update imports:
// use thiserror::Error; // Replace this
use Error; // With this
Step 3: Your existing code works unchanged! Optionally add new features like location tracking.
Detailed Features
wherror extends thiserror with community-requested features while maintaining thiserror API compatibility. All existing thiserror code works unchanged.
-
Errors may be enums, structs with named fields, tuple structs, or unit structs.
-
A
Displayimpl is generated for your error if you provide#[error("...")]messages on the struct or each variant of your enum, as shown above in the example.The messages support a shorthand for interpolating fields from the error.
#[error("{var}")]ββΆβwrite!("{}", self.var)#[error("{0}")]ββΆβwrite!("{}", self.0)#[error("{var:?}")]ββΆβwrite!("{:?}", self.var)#[error("{0:?}")]ββΆβwrite!("{:?}", self.0)
These shorthands can be used together with any additional format args, which may be arbitrary expressions. For example:
# use i32; # use Error; #If one of the additional expression arguments needs to refer to a field of the struct or enum, then refer to named fields as
.varand tuple fields as.0.# use Error; # # # # # # -
A
Fromimpl is generated for each variant that contains a#[from]attribute.The variant using
#[from]must not contain any other fields beyond the source error (and possibly a location or backtrace β see below). Usually#[from]fields are unnamed, but#[from]is allowed on a named field too.# use ; # use io; # use Error; # # # # #For
Box<T>fields with#[from], bothFrom<Box<T>>andFrom<T>implementations are automatically generated for enhanced ergonomics:# use io; # use Error; # # # -
Use
#[error(debug)]as a fallback to automatically generate Display implementations using the Debug format. This eliminates boilerplate when your enum variant names are already descriptive error messages.This addresses the request in thiserror#172 for optional error messages, allowing you to skip redundant
#[error("TooSmall")]whenTooSmallis already a clear error name.For enums, you can apply
#[error(debug)]at the type level to automatically generate Display for all variants that don't have explicit#[error("...")]messages:# use Error; # // fallback for variants without explicit messagesYou can also apply
#[error(debug)]to individual variants or struct types:# use Error; # // Entire struct uses Debug formatting -
The Error trait's
source()method is implemented to return whichever field has a#[source]attribute or is namedsource, if any. This is for identifying the underlying lower level error that caused your error.The
#[from]attribute always implies that the same field is#[source], so you don't ever need to specify both attributes.Any error type that implements
std::error::Erroror dereferences todyn std::error::Errorwill work as a source.# use ; # use Error; # # # -
Fields of type
&'static std::panic::Location<'static>are automatically populated with the call site location when errors are created viaFromtrait conversion. This works seamlessly with the?operator for precise error tracking.wherror automatically generates a
.location()method that returnsOption<&'static std::panic::Location<'static>>for easy access to error origins.This implements the feature requested in thiserror#142 (17π).
# use Error; # # -
The Error trait's
provide()method is implemented to provide whichever field has a type namedBacktrace, if any, as astd::backtrace::Backtrace. UsingBacktracein errors requires a nightly compiler with Rust version 1.73 or newer.# use Backtrace; # use Error; # -
If a field is both a source (named
source, or has#[source]or#[from]attribute) and is marked#[backtrace], then the Error trait'sprovide()method is forwarded to the source'sprovideso that both layers of the error share the same backtrace. The#[backtrace]attribute requires a nightly compiler with Rust version 1.73 or newer.# use io; # use Error; # -
For variants that use
#[from]and also contain aBacktracefield, a backtrace is captured from within theFromimpl.# use Backtrace; # use io; # use Error; # -
Errors may use
error(transparent)to forward the source and Display methods straight through to an underlying error without adding an additional message. This would be appropriate for enums that need an "anything else" variant.# use wherror::Error; # #[derive(Error, Debug)] pub enum MyError { # /* ... # */ #[error(transparent)] Other(#[from] anyhow::Error), // source and Display delegate to anyhow::Error }Another use case is hiding implementation details of an error representation behind an opaque error type, so that the representation is able to evolve without breaking the crate's public API.
# use wherror::Error; # // PublicError is public, but opaque and easy to keep compatible. #[derive(Error, Debug)] #[error(transparent)] pub struct PublicError(#[from] ErrorRepr); impl PublicError { // Accessors for anything we do want to expose publicly. } // Private and free to change across minor version of the crate. #[derive(Error, Debug)] enum ErrorRepr { # /* ... # */ } -
See also the
anyhowlibrary for a convenient single error type to use in application code.
Comparison to anyhow
Use wherror if you care about designing your own dedicated error type(s) so that the caller receives exactly the information that you choose in the event of failure. This most often applies to library-like code. Use Anyhow if you don't care what error type your functions return, you just want it to be easy. This is common in application-like code.
License
Attribution
License: MIT OR Apache-2.0