dtolnay/anyhow

View on GitHub

Flexible concrete Error type built on std::error::Error

Stars: 6.7k
Forks: 224
Open beginner issues: 0
Indexed issues: 37

Dominant language: Rust
License: Apache-2.0
Last GitHub push: Aug 22, 2026
Latest indexed: Sep 15, 2026
Contributing guide: No contributing guide
Code of conduct: Code of conduct
Beginner labels: No beginner labels indexed
PR merge metrics: No merged PRs in 30d

Open All

37 open issues indexed

downcasting on individual context layers Open

dtolnay/anyhow#84 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 15, 2026
RFC: Add support for customizable error handlers based on `eyre` Open

dtolnay/anyhow#96 · 1 comment · 6 reactions · 0 assignees · Indexed Sep 15, 2026
Default {} is confusing, while {:#} is much better Open

dtolnay/anyhow#111 · 3 comments · 20 reactions · 0 assignees · Indexed Sep 15, 2026
Attach line & file info to anyhow::Error and anyhow::Context Open

dtolnay/anyhow#139 · 9 comments · 47 reactions · 0 assignees · Indexed Sep 15, 2026
Upper or lower case error messages? Open

dtolnay/anyhow#209 · 1 comment · 10 reactions · 0 assignees · Indexed Sep 15, 2026
Recommendation on mixing exit codes with anyhow Open

dtolnay/anyhow#247 · 7 comments · 28 reactions · 0 assignees · Indexed Sep 15, 2026
Why does Error::downcast<E> and Error::is<E> require E: Debug Open

dtolnay/anyhow#270 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Option to print error with causes multiline but no backtrace Open

dtolnay/anyhow#300 · 0 comments · 6 reactions · 0 assignees · Indexed Sep 15, 2026
Make Error::from_std public Open

dtolnay/anyhow#301 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
[Question] In `{:#?}` why is the outermost context called "caused by" and how is `Context` expected to be used? Open

dtolnay/anyhow#324 · 1 comment · 1 reaction · 0 assignees · Indexed Sep 15, 2026
Customize backtrace logic? Open

dtolnay/anyhow#328 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
`anyhow!(e)` doesn't preserve `source` for `&Error` Open

dtolnay/anyhow#341 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Make backtrace support optional Open

dtolnay/anyhow#346 · 10 comments · 15 reactions · 0 assignees · Indexed Sep 15, 2026
Possible performance regression on Windows Open

dtolnay/anyhow#347 · 5 comments · 2 reactions · 0 assignees · Indexed Sep 15, 2026
as_ref() type must be known at this point Open

dtolnay/anyhow#348 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Implement Context for Error Open

dtolnay/anyhow#352 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Question regarding stacktrace Open

dtolnay/anyhow#353 · 0 comments · 1 reaction · 0 assignees · Indexed Sep 15, 2026
anyhow::Error to Box<dyn Error> isn't compatible with other libraries Open

dtolnay/anyhow#356 · 5 comments · 1 reaction · 0 assignees · Indexed Sep 15, 2026
Are you open to de-duplicating the build.rs build probe code? Open

dtolnay/anyhow#359 · 7 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Short backtrace Open

dtolnay/anyhow#362 · 2 comments · 1 reaction · 0 assignees · Indexed Sep 15, 2026
This library almost disables multithreading while used with `RUST_BACKTRACE=1` Open

dtolnay/anyhow#380 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Add a programmable switch for backtrace Open

dtolnay/anyhow#381 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Feature request / discuss: allow errors to have multiple causes Open

dtolnay/anyhow#387 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Add debugger visualizer for anyhow::Error Open

dtolnay/anyhow#394 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
serde_json::Error locations are omitted from the backtrace Open

dtolnay/anyhow#400 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Reconsider stracktrace configurability with rust 2024 set_var changes. Open

dtolnay/anyhow#403 · 1 comment · 3 reactions · 0 assignees · Indexed Sep 15, 2026
Creating anyhow! from Arc<Error> miss error source Open

dtolnay/anyhow#405 · 2 comments · 3 reactions · 0 assignees · Indexed Sep 15, 2026
Increase or remove `ensure` `Debug` output limit Open

dtolnay/anyhow#406 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Readme claims backtraces captured "if the underlying error type does not already provide its own" Open

dtolnay/anyhow#409 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Add more data when chaining errors. Open

dtolnay/anyhow#418 · 0 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
User input in error message may poison logs with ANSI escape sequences Open

dtolnay/anyhow#424 · 2 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Compilation feature for alt-display by default Open

dtolnay/anyhow#427 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 15, 2026
What is the most robust way of downcasting an `anyhow::Error`? Open

dtolnay/anyhow#431 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 15, 2026
REQUEST: Add method to iterate entire context chain, not just errors Open

dtolnay/anyhow#434 · 1 comment · 1 reaction · 0 assignees · Indexed Sep 15, 2026
Missing copyright notice needed for Apache 2.0 license Open

dtolnay/anyhow#443 · 2 comments · 0 reactions · 0 assignees · Indexed Sep 15, 2026
Nightly probe ignores CARGO_UNSTABLE_ALLOW_FEATURES Open

dtolnay/anyhow#453 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 15, 2026
`ensure!` doesn't accept inline const blocks Open

dtolnay/anyhow#458 · 1 comment · 0 reactions · 0 assignees · Indexed Sep 15, 2026

dtolnay/anyhow

Get new issues in your inbox