Comments (2)
Yes -- if you deref first to &std::error::Error then you get the standard library's downcast implementation which is nonrecursive.
use anyhow::{anyhow, Error};
use std::fmt::{self, Debug, Display};
pub struct Internal(Error);
impl std::error::Error for Internal {
fn source(&self) -> Option<&(dyn std::error::Error + 'static)> {
self.0.source()
}
}
impl Debug for Internal {
fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
Debug::fmt(&self.0, f)
}
}
impl Display for Internal {
fn fmt(&self, f: &mut fmt::Formatter) -> fmt::Result {
Display::fmt(&self.0, f)
}
}
fn main() {
let e0 = anyhow!("e0");
let e1 = e0.context("e1");
let e2 = e1.context("e2");
let e2_internal = anyhow!(Internal(e2));
let e3 = e2_internal.context("e3");
let e4 = e3.context("e4");
println!("recursive downcast: {}", e4.downcast_ref::<Internal>().is_some());
println!("nonrecursive downcast: {}", (*e4).downcast_ref::<Internal>().is_some());
for e in e4.chain() {
println!("{} {}", e, e.downcast_ref::<Internal>().is_some());
}
}
recursive downcast: true
nonrecursive downcast: false
e4 false
e3 false
e2 true
e1 false
e0 false
from anyhow.
Oh for some reason I thought that the standard library implementation would have the same behavior via an override, but I see now that's not even possible much less not even the case! Thanks!
from anyhow.
Related Issues (20)
- Couldn't use with nom error HOT 2
- the following trait bounds were not satisfied: `(): anyhow::context::ext::StdError` HOT 1
- Use `#[track_caller]` to provide info on where the error was created HOT 1
- Allow source errors to expose their own context? HOT 1
- `build.rs` should not detect nightly feature HOT 11
- [Question] In `{:#?}` why is the outermost context called "caused by" and how is `Context` expected to be used? HOT 1
- `ensure!` macro implementation details HOT 8
- Nightly feature wrongly enabled on stable toolchain HOT 3
- Should `anyhow::Error::chain` return `dyn Error + Send + Sync` HOT 2
- Customize backtrace logic?
- `anyhow!(e)` doesn't preserve `source` for `&Error` HOT 1
- A way to disable anyhow stacktraces (without disabling stacktraces from other crates) HOT 2
- Default Ok-type to `()` in `anyhow::Result` typedef HOT 2
- Updating from version 1.0.76 breaks backtraces HOT 2
- Make backtrace support optional HOT 9
- Possible performance regression on Windows HOT 5
- as_ref() type must be known at this point
- Depending on `CARGO_ENCODED_RUSTFLAGS` may produce stale builds HOT 1
- rust-analyzer nightly throws needless_return warning on bail! HOT 2
- Implement Context for Error
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from anyhow.