1.0.31

• Restore "Stack backtrace" header label above the backtrace in {:?} representation (#92)

1.0.30

• Hide an error message that appears when building with cargo rustc -vv (#91, thanks @eoger)

1.0.29

• Documentation improvements

1.0.28

• Documentation improvements (#73, #78)

1.0.27

• Improve documentation of backtrace environment variable combinations (#69)

  • If you want panics and errors to both have backtraces, set RUST_BACKTRACE=1;
  • If you want only errors to have backtraces, set RUST_LIB_BACKTRACE=1;
  • If you want only panics to have backtraces, set RUST_BACKTRACE=1 and RUST_LIB_BACKTRACE=0.

1.0.26

• Fix indentation when printing causes that have a multiline error message (#54, thanks @yaahc)

1.0.25

• Add no-std support (#53)

  In no_std mode, the same API is almost all available and works the same way. To depend on Anyhow in no_std mode, disable our default enabled "std" feature in Cargo.toml. A global allocator is required.

  [dependencies]
  anyhow = { version = "1.0", default-features = false }

  Since the ?-based error conversions would normally rely on the std::error::Error trait which is only available through std, no_std mode will require an explicit .map_err(Error::msg) when working with a non-Anyhow error type inside a function that returns Anyhow's error type.

1.0.24

• Preserve cause chain when converting from Box<dyn StdError + Send + Sync> to anyhow::Error (#50)
• Work around bug in NixOS package infrastructure (#49)

1.0.23

• Add impl AsRef<dyn std::error::Error> and impl AsRef<dyn std::error::Error + Send + Sync> for anyhow::Error
• Add Chain::new constructor

1.0.22

• Preserve cause chain when bail! or ensure! is invoked with anyhow::Error as the error argument (#46)