NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
crates.io · #1426 most downloaded on crates.io
derives for the failure crate
Last release 6 years ago
no release in 18 months
Release timing varies
gaps range from 2 weeks to 10 months
Most releases are documented
notes for 7 of 10 stable releases
Nothing withdrawn
no release was ever pulled
9 years old
10 releases · first in 2017
Nothing published for this version
Nothing published for this version
Update syn, quote, and proc_macro2 dependencies to 1.0.
syn, quote, and proc_macro2 dependencies to 1.0.One column per quarter.
Added missing changelog entry for name
Added missing changelog entry for name
name() to Fail and ErrorImproved error reporting of the derive feature
Fixed a memory leak for older rust versions on error downcast
Context::mapDeprecate Fail::causes and ::causes in favor of newly added ::iter_causes.
The original plan to release 1.0.0 was changed so that version 0.1.1 is released and a related RFC to fix the error trait is submitted. See README for details.
failure_derive to work with Rust 2018.#[fail(cause)] that works similarly with #[cause]. The new form is preferred."backtrace" feature to work without "std" feature.Compat::get_ref.Fallible.Fail::causes and <dyn Fail>::causes in favor of newly added <dyn Fail>::iter_causes.Fail::root_cause and <dyn Fail>::root_cause in favor of newly added <dyn Fail>::find_root_cause.<dyn Fail>::iter_chain.Box<Fail>: Fail.Error::from_boxed_compat.Error::cause in favor of newly added Error::as_fail.Error::causes in favor of newly added Error::iter_chain.Error::root_cause in favor of newly added Error::find_root_cause.Error::iter_causes.Error: AsRef<Fail>.Debug implementation of SyncFailure.Add a Causes iterator, which iterates over the causes of a failure. Can be accessed through the Fail::causes or Error::causes methods.
Causes iterator, which iterates over the causes of a failure. Can be
accessed through the Fail::causes or Error::causes methods.bail! macro, which "throws" from the function.ensure! macro, which is like an "assert" which throws instead of
panicking.failure by default, so that users do not
have to directly depend on failure_derive.From<D> for Context<D>, allowing users to ? the D type to
produce a Context<D> (for cases where there is no further underlying
error).- Initial version.
Nothing published for this version
Your coding agent can read these notes before it upgrades. Set up the MCP server →