dtolnay/anyhow issues and pull requests

#305 - macro anyhow::format_err is duplicated with macro anyhow?

Issue - State: closed - Opened by gftea almost 2 years ago - 1 comment

#304 - Add `core-error` feature to allow semantic use of `anyhow` in no_std

Issue - State: closed - Opened by semiviral almost 2 years ago - 1 comment

#303 - Add support for wasm_bindgen

Pull Request - State: closed - Opened by starua almost 2 years ago - 1 comment

#302 - Update to syn 2

Pull Request - State: closed - Opened by dtolnay almost 2 years ago

#301 - Make Error::from_std public

Issue - State: open - Opened by stepancheg almost 2 years ago

#300 - Option to print error with causes multiline but no backtrace

Issue - State: open - Opened by stepancheg almost 2 years ago

#299 - Get the downcast and underlying error message of the enum

Issue - State: closed - Opened by 0cv almost 2 years ago - 1 comment

#298 - Support const block syntax in ensure! macro

Pull Request - State: closed - Opened by dtolnay almost 2 years ago

#297 - anyhow Debug trail impl uses the Display for all the errors in the chain and not Debug

Issue - State: closed - Opened by DanielBauman88 about 2 years ago - 2 comments

#296 - Result<...> Deserialize error

Issue - State: closed - Opened by Virgil-N about 2 years ago - 1 comment

#295 - Hide repr attribute from documentation

Pull Request - State: closed - Opened by dtolnay about 2 years ago

#294 - make ensure!() return Ok(())

Issue - State: closed - Opened by aruediger about 2 years ago - 2 comments

#293 - Enable backtrace support for >= 1.65 stable compilers

Pull Request - State: closed - Opened by LukasKalbertodt about 2 years ago - 2 comments

#292 - Related errors

Issue - State: closed - Opened by andrewbaxter about 2 years ago - 1 comment

#291 - Anhow Doesn't compile

Issue - State: closed - Opened by redfer13 about 2 years ago - 2 comments

#290 - Customize output format

Issue - State: closed - Opened by fritzrehde about 2 years ago - 1 comment

#289 - anyhow `v1.0.66` leaks some nightly flags

Issue - State: closed - Opened by sassman about 2 years ago - 2 comments

#288 - Rust analiser keeps prompting errors when upgrade to 1.65 stable toolchain

Issue - State: closed - Opened by CoorFun about 2 years ago - 1 comment

#287 - Feature: track caller

Pull Request - State: closed - Opened by har7an about 2 years ago - 2 comments

#286 - `#![feature]` may not be used on the stable release channel error reappears in latest version 1.0.66

Issue - State: closed - Opened by fishseabowl about 2 years ago - 1 comment

#285 - Add note to backtrace stabilize

Pull Request - State: closed - Opened by tomocrafter over 2 years ago - 1 comment

#284 - Use `std::backtrace::Backtrace` even on the stable channel

Issue - State: closed - Opened by laralove143 over 2 years ago

#283 - Update backtrace documentation for Rust 1.65 release

Pull Request - State: closed - Opened by laralove143 over 2 years ago - 1 comment

#282 - 1.0 doesn't compile in stable channel

Issue - State: closed - Opened by kkolyan over 2 years ago - 1 comment

#281 - Remove redundant Backtrace provide_ref from ContextError

Pull Request - State: closed - Opened by dtolnay over 2 years ago

#280 - Remove 2 frames of backtrace noise on Option's Context impl

Pull Request - State: closed - Opened by dtolnay over 2 years ago

#279 - Remove 2 frames of noise from 'context' backtraces

Pull Request - State: closed - Opened by dtolnay over 2 years ago

#278 - Support automatic tagging of errors with location?

Issue - State: closed - Opened by kevinushey over 2 years ago - 1 comment

#277 - Should Anyhow include features for library-specific integrations?

Issue - State: closed - Opened by T-O-R-U-S over 2 years ago - 1 comment

#276 - Marking the `Result` type as `#[must_use]`

Issue - State: closed - Opened by ClementNerma over 2 years ago - 2 comments

#275 - kind() method not found in anyhow::Error

Issue - State: closed - Opened by ptdecker over 2 years ago - 1 comment

#274 - Should there be an `impl std::error::Error for anyhow::Error`?

Issue - State: closed - Opened by nathan-at-least over 2 years ago - 1 comment

#272 - README does not explain what problem crate solves (how crate compares to std)

Issue - State: closed - Opened by hkBst over 2 years ago - 1 comment

#271 - impl std::any::Provider for anyhow::Error

Pull Request - State: closed - Opened by dtolnay over 2 years ago

#270 - Why does Error::downcast<E> and Error::is<E> require E: Debug

Issue - State: open - Opened by tomaspecl over 2 years ago

#268 - Include outer backtrace when called as source.provide

Pull Request - State: closed - Opened by dtolnay over 2 years ago

#267 - Rename &mut Demand arguments to 'demand'

Pull Request - State: closed - Opened by dtolnay over 2 years ago

#266 - Use backtrace via generic member access

Pull Request - State: closed - Opened by dtolnay over 2 years ago - 2 comments

#265 - should we call `.into()` in `bail!`?

Issue - State: closed - Opened by M1cha over 2 years ago - 1 comment

#262 - How to use backtrace after stabilisation?

Issue - State: closed - Opened by Morganamilo over 2 years ago - 8 comments

#261 - 1.0.61 causes rebuilds after restarting VScode with rust-analyzer

Issue - State: closed - Opened by NeoRaider over 2 years ago - 3 comments

#260 - Workaround for IntelliJ plugin

Pull Request - State: closed - Opened by wmdrichards over 2 years ago - 1 comment

#258 - Add link to Cargo RUSTC_WRAPPER PR

Pull Request - State: closed - Opened by dtolnay over 2 years ago

#256 - Implement Cargo feature: prohibit_backtrace

Pull Request - State: closed - Opened by vi over 2 years ago - 5 comments

#254 - "method `backtrace` is not a member of trait `StdError`"

Issue - State: closed - Opened by Berrysoft over 2 years ago - 6 comments

#253 - 1.0.61 broken support for Rust 1.48

Issue - State: closed - Opened by davidhewitt over 2 years ago - 2 comments

#252 - Work around RA's RUSTC_WRAPPER poisoning all subsequent command-line builds

Pull Request - State: closed - Opened by dtolnay over 2 years ago - 2 comments

#251 - work around RAs RUSTC_WRAPPER hack

Pull Request - State: closed - Opened by RalfJung over 2 years ago - 8 comments

#250 - "#![feature] may not be used on the stable release channel"

Issue - State: closed - Opened by silmeth over 2 years ago - 25 comments

#249 - propagate --target to rustc invocation

Pull Request - State: closed - Opened by RalfJung over 2 years ago - 3 comments

#248 - build.rs checks for CARGO_RUSTC_WRAPPER which does not seem to be a thing

Issue - State: closed - Opened by RalfJung over 2 years ago - 2 comments

#247 - Recommendation on mixing exit codes with anyhow

Issue - State: open - Opened by chipsenkbeil over 2 years ago - 2 comments

#246 - Re-enable backtrace test on miri

Issue - State: closed - Opened by dtolnay over 2 years ago - 5 comments

#245 - Add a clonable ArcError/ArcResult

Issue - State: closed - Opened by ssbr over 2 years ago - 3 comments

#244 - The scope of the unsafe block can be appropriately reduced

Pull Request - State: closed - Opened by peamaeq over 2 years ago

#243 - panic when try to convert IO errors into anyhow::Error

Issue - State: closed - Opened by jm-observer over 2 years ago - 2 comments

#242 - Update docs.rs badge

Pull Request - State: closed - Opened by M3DZIK over 2 years ago

#241 - Debug representation of anyhow::Error does not use Debug representation of underlying error

Issue - State: closed - Opened by JK-WP over 2 years ago - 1 comment

#240 - How to make Error cloneable and support context chaining

Issue - State: closed - Opened by FredrikNoren over 2 years ago - 3 comments

#239 - Cannot opt out of backtrace feature on nigthly.

Issue - State: closed - Opened by vi almost 3 years ago - 2 comments

#238 - [Question] How to chain anyhow errors ?

Issue - State: closed - Opened by Cheappie almost 3 years ago - 3 comments

#237 - Enahncement: impl Context for TryFutureExt

Issue - State: closed - Opened by detly almost 3 years ago - 1 comment

#236 - Does an unwrap equivilant trait exist for option/types?

Issue - State: closed - Opened by peepo5 almost 3 years ago - 2 comments

#235 - Question regarding coding style

Issue - State: closed - Opened by tomers almost 3 years ago - 4 comments

#234 - Incorrect format argument handling while using captured identifiers in format string

Issue - State: closed - Opened by winterqt almost 3 years ago - 2 comments

#232 - implement From for Option

Issue - State: closed - Opened by laralove143 almost 3 years ago - 4 comments

#231 - anyhow's dyn error `backtrace` disagrees with `anyhow::Error::backtrace`

Issue - State: closed - Opened by guswynn almost 3 years ago - 2 comments

#230 - Build fails when -Zallow-features doesn't include backtrace

Issue - State: closed - Opened by bjorn3 almost 3 years ago - 4 comments

#229 - Add must_use to Error constructors

Pull Request - State: closed - Opened by dtolnay almost 3 years ago

#228 - Annotate anyhow::Error as #[must_use]

Pull Request - State: closed - Opened by davidlattimore almost 3 years ago - 2 comments

#226 - Tracing's `instrument(err)` when returning anyhow::Result

Issue - State: closed - Opened by dtolnay almost 3 years ago - 1 comment

#225 - Changelog for latest release

Issue - State: closed - Opened by Sytten almost 3 years ago - 1 comment

#222 - Can I change the `Error` prefix?

Issue - State: closed - Opened by mauro-balades about 3 years ago - 2 comments

#221 - Using {:#?} to try and prettyprint an anyhow error with backtrace enabled suppresses the backtrace

Issue - State: closed - Opened by DanielJoyce about 3 years ago - 4 comments

#220 - Call bail on an interop with thiserror

Issue - State: closed - Opened by nipunn1313 about 3 years ago - 2 comments

#209 - Upper or lower case error messages?

Issue - State: open - Opened by matklad about 3 years ago - 1 comment

#175 - Clarify how to print out backtraces in the docs

Issue - State: closed - Opened by samuela over 3 years ago - 2 comments
Labels: docs

#172 - Using TryFrom/TryInto generics with anyhow::Error

Issue - State: closed - Opened by kpcyrd over 3 years ago - 1 comment
Labels: support

#163 - Allow converting anyhow::Error to impl StdError

Pull Request - State: closed - Opened by kangalio over 3 years ago

#153 - Pass anyhow::Error where impl Error is expected

Issue - State: closed - Opened by hniksic almost 4 years ago - 6 comments

#139 - Attach line & file info to anyhow::Error and anyhow::Context

Issue - State: open - Opened by vultix about 4 years ago - 9 comments

#136 - anyhow::Error does not implement std::error::Error

Issue - State: closed - Opened by L-as about 4 years ago - 5 comments

#135 - Context returned by `Error::chain` can't be downcast to original type

Issue - State: closed - Opened by genbattle about 4 years ago - 3 comments

#125 - `ensure!()` doesn't work in `try` blocks because it calls `return`

Issue - State: closed - Opened by Boscop over 4 years ago - 4 comments

#123 - Retrieve full error message from type-erased anyhow::Error

Issue - State: closed - Opened by hniksic over 4 years ago - 4 comments

#119 - How reliable is the Debug implementation of anyhow::Error?

Issue - State: closed - Opened by stevenroose over 4 years ago - 2 comments

#118 - What is the MSRV policy of this crate

Issue - State: closed - Opened by stevenroose over 4 years ago - 1 comment

#112 - `ensure!` does not call `from`

Issue - State: closed - Opened by leoyvens over 4 years ago - 6 comments

#111 - Default {} is confusing, while {:#} is much better

Issue - State: open - Opened by ndmitchell over 4 years ago - 3 comments

#102 - question: is `anyhow::Error/Result` a proper choice for method signatures of the library API (as opposed to internal use in the final application) ?

GitHub / dtolnay/anyhow issues and pull requests