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.
You sometimes need a layer of Box<Error> in an API when e.g. making a pluginizable framework. You can currently propagate the cause chain up properly but not a backtrace.
It would be nice if ChainedError were split with a top-level trait which just extends Error and has extract_backtrace and error_chain! were updated to allow propagation of the backtrace through it. Something like
error_chain! {
errors {
Plugin(e: Box<BaseChainedError>) {
cause(e)
backtrace(e)
description("error from a plugin")
display("error from a plugin: {}", e)
}
}
}
The text was updated successfully, but these errors were encountered:
You sometimes need a layer of
Box<Error>
in an API when e.g. making a pluginizable framework. You can currently propagate the cause chain up properly but not a backtrace.It would be nice if
ChainedError
were split with a top-level trait which just extendsError
and hasextract_backtrace
anderror_chain!
were updated to allow propagation of the backtrace through it. Something likeThe text was updated successfully, but these errors were encountered: