Skip to content

docs: clarify backtrace detection limitation on stable Rust #460

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.

Sign up for GitHub

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

Open
atheerium wants to merge 1 commit into
base: master
Choose a base branch
from
+6 −0
Open

docs: clarify backtrace detection limitation on stable Rust #460

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -88,6 +88,12 @@ anyhow = "1.0"

[`std::backtrace`]: https://doc.rust-lang.org/std/backtrace/index.html#environment-variables

> **Note:** Whether anyhow can detect that an underlying error type already
> provides its own backtrace depends on the unstable
> `error_generic_member_access` feature. When that feature is not
> available (stable Rust), anyhow always captures its own backtrace
> regardless of whether the underlying error has one.

- Anyhow works with any error type that has an impl of `std::error::Error`,
including ones defined in your crate. We do not bundle a `derive(Error)` macro
but you can write the impls yourself or use a standalone macro like
Expand Down