-
-
Notifications
You must be signed in to change notification settings - Fork 168
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Deriving structs with backtrace
fails since fn backtrace
has been removed from Error
#177
Comments
This comment was marked as spam.
This comment was marked as spam.
astraw
added a commit
to strawlab/strand-braid
that referenced
this issue
Aug 6, 2022
This is blocked on rust-lang/rust#100399. |
Perhaps not — it looks like |
Do we need to remove the backtrace method? Lines 62 to 104 in 1442e27
|
uonr
pushed a commit
to mythal/boluo-mono
that referenced
this issue
Aug 20, 2022
ariel-miculas
added a commit
to ariel-miculas/puzzlefs
that referenced
this issue
Nov 15, 2022
Fixes project-machine#47 Unfortunately, deleting the custom Display implementation results in ugly stacktraces (condensed into one long line instead of pretty printed) in tests, see 8049c6a for context. This implementation doesn't work because 'fn backtrace' is not part of 'Error' anymore. See: dtolnay/thiserror#177 and dtolnay/anyhow#111 Signed-off-by: Ariel Miculas <amiculas@cisco.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
As of rust-lang/rust#99431
fn backtrace
is not part ofError
anymore. This causes derives withbacktrace
to fail; And the following example results in a compilation error.The text was updated successfully, but these errors were encountered: