Skip to content

Issues: dtolnay/anyhow

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

26 Open 180 Closed
26 Open 180 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Feature request / discuss: allow errors to have multiple causes
#387 opened Oct 4, 2024 by sxlijin
Add a programmable switch for backtrace
#381 opened Jul 30, 2024 by xtexChooser
This library almost disables multithreading while used with RUST_BACKTRACE=1
#380 opened Jul 12, 2024 by nickkuk
Conversion to Box<dyn Error> loses downcast ability
#379 opened Jul 5, 2024 by seanmonstar
1
Short backtrace
#362 opened Apr 21, 2024 by thewh1teagle
2
Are you open to de-duplicating the build.rs build probe code?
#359 opened Mar 26, 2024 by RalfJung
7
anyhow::Error to Box<dyn Error> isn't compatible with other libraries
#356 opened Mar 13, 2024 by rkuklik
2
Question regarding stacktrace
#353 opened Mar 7, 2024 by oknozor
Implement Context for Error
#352 opened Mar 5, 2024 by mawallace
as_ref() type must be known at this point
#348 opened Feb 3, 2024 by pronebird
Possible performance regression on Windows
#347 opened Jan 26, 2024 by nwalfield
5
Make backtrace support optional
#346 opened Jan 14, 2024 by purplesyringa
10
anyhow!(e) doesn't preserve source for &Error
#341 opened Jan 3, 2024 by xxchan
1
Customize backtrace logic?
#328 opened Dec 15, 2023 by quark-zju
Should anyhow::Error::chain return dyn Error + Send + Sync
#327 opened Nov 28, 2023 by ten3roberts
2
[Question] In {:#?} why is the outermost context called "caused by" and how is Context expected to be used?
#324 opened Oct 26, 2023 by nathan-at-least
1
Make Error::from_std public
#301 opened Mar 17, 2023 by stepancheg
Option to print error with causes multiline but no backtrace
#300 opened Mar 17, 2023 by stepancheg
Why does Error::downcast<E> and Error::is<E> require E: Debug
#270 opened Sep 7, 2022 by tomaspecl
Recommendation on mixing exit codes with anyhow
#247 opened Jul 25, 2022 by chipsenkbeil
2
Upper or lower case error messages?
#209 opened Dec 6, 2021 by matklad
1
Attach line & file info to anyhow::Error and anyhow::Context
#139 opened Feb 5, 2021 by vultix
8
Default {} is confusing, while {:#} is much better
#111 opened Sep 4, 2020 by ndmitchell
3
RFC: Add support for customizable error handlers based on eyre
#96 opened Jun 6, 2020 by yaahc
1
downcasting on individual context layers
#84 opened Apr 9, 2020 by danburkert
1
ProTip! Find all open issues with in progress development work with linked:pr.