Skip to content

docs: clarify backtrace detection limitation on stable Rust - #460

Open
atheerium wants to merge 1 commit into
dtolnay:masterfrom
atheerium:fix/readme-backtrace-note
Open

docs: clarify backtrace detection limitation on stable Rust#460
atheerium wants to merge 1 commit into
dtolnay:masterfrom
atheerium:fix/readme-backtrace-note

Conversation

@atheerium

Copy link
Copy Markdown

The README states that backtraces are captured 'if the underlying error type does not already provide its own,' but this behavior depends on the unstable error_generic_member_access feature. On stable Rust, anyhow always captures its own backtrace. Adds a clarifying note.

Addresses #409

The README claims backtraces are captured "if the underlying error type
does not already provide its own", but this behavior depends on the
unstable  feature. On stable Rust, anyhow
always captures its own backtrace regardless.

Add a note explaining this to avoid misleading users.

Addresses dtolnay#409
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant