You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 16, 2021. It is now read-only.
The AsFail implementation for Error only looks for a backtrace on the underlying Fail, and skips backtraces attached directly to the Error. This means that Errors constructed from implementors of the std::error::Error trait lose their backtraces when they are used as a cause.
The text was updated successfully, but these errors were encountered:
Confusion around this resulted in rust-lang/crater#455. Ideally, Error would implement Fail, but this is impossible due to coherence issues (#99). Absent that, it would be nice if there was a way to abstract over both Error and Context without throwing away the Backtrace.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The
AsFail
implementation forError
only looks for a backtrace on the underlyingFail
, and skips backtraces attached directly to theError
. This means thatError
s constructed from implementors of thestd::error::Error
trait lose their backtraces when they are used as a cause.The text was updated successfully, but these errors were encountered: