openv
openv copied to clipboard
Update Rust crate anyhow to 1.0.70
This PR contains the following updates:
Package | Type | Update | Change |
---|---|---|---|
anyhow | dependencies | patch | 1.0.37 -> 1.0.70 |
Release Notes
dtolnay/anyhow
v1.0.70
- Update syn dependency to 2.x
v1.0.69
- Documentation improvements
v1.0.68
- Opt out of
-Zrustdoc-scrape-examples
on docs.rs for now
v1.0.67
- Improve the backtrace captured when
context()
is used on anOption
(#280)
v1.0.66
- Reduce unhelpful backtrace frames in backtraces captured during a
context
call (#279)
v1.0.65
-
impl Provider for anyhow::Error
v1.0.64
v1.0.63
- Expose backtraces via the new "generic member access" API on the Error trait (https://github.com/rust-lang/rust/issues/99301, https://github.com/rust-lang/rust/issues/96024)
v1.0.62
- Fix extra rebuilding when interleaving command-line
cargo
invocations with IDE builds (#261)
v1.0.61
- Work around rust-analyzer builds poisoning all subsequent command-line cargo builds (#252)
v1.0.60
- Propagate
--target
to rustc invocation when deciding about backtrace support (#249, thanks @RalfJung)
v1.0.59
- Update crates.io metadata to include
no-std
category
v1.0.58
- Fix some broken links in documentation
v1.0.57
- Remove a
log4rs
-specific workaround frombail!
macro implementation
v1.0.56
- Add
must_use
warning when an Error created byanyhow!
is not used, perhaps because the programmer meant to writebail!
instead (#229)
v1.0.55
- Documentation improvements
v1.0.54
- Construct more helpful error message from
ensure!
when the expression involves a negative literal const generic as the first generic argument of a method call (#224)
v1.0.53
- Retrigger docs.rs build to work around rustdoc regression (https://github.com/rust-lang/rust/issues/92331)
v1.0.52
- Reduce overhead of backtrace capture in the case that backtraces are not enabled (#212)
v1.0.51
- Show doc for
Ok
fn
v1.0.50
- Recognize more types of expressions in
ensure!
macro (#199, #200, #202, #203, #204, #205, #206)
v1.0.49
- Add a function
anyhow::Ok(v)
equivalent toOk::<_, anyhow::Error>(v)
(#192)
v1.0.48
- Include a
Debug
rendering of lhs and rhs inensure!
messages (#193, #194, #195, #196, #197, #198)
Example:
```rust
ensure!(flags.len() <= 40);
```
```rust
ensure!(kind == Kind::File);
```
Before:
```console
Condition failed: `flags.len() <= 40`
Condition failed: `kind == Kind::File`
```
After:
```console
Condition failed: `flags.len() <= 40` (99 vs 40)
Condition failed: `kind == Kind::File` (Symlink vs File)
```
v1.0.47
- Fixes for implicit format args support
v1.0.46
-
Support for implicit format args to match println and other std macros (https://rust-lang.github.io/rfcs/2795-format-args-implicit-identifiers.html)
let var = ...; let error = anyhow!("interpolate {var}"); // equivalent to anyhow!("interpolate {var}", var=var)
-
Detect missing fmt arguments at compile time:
anyhow!("{} not found")
(#55) -
Reduce occurrence of "future cannot be shared between threads safely" in async code using anyhow macros (#186)
v1.0.45
- Fix non-compilable macro expansion if downstream crate calls
anyhow!
,ensure!
, orbail!
with format args and is built with#![no_std]
or#![no_implicit_prelude]
(#177)
v1.0.44
- Mark error constructors cold to help LLVM optimize code paths not leading to error (#166, thanks @stepancheg)
v1.0.43
- Take -Zallow-features restrictions from Cargo configuration file into account on sufficiently new versions of nightly Cargo (#157, thanks @jonhoo)
v1.0.42
- Enable Android's automated tooling to pull in test coverage improvements
v1.0.41
- Disallow incompatible old versions of backtrace crate (#155, thanks @jfirebaugh)
v1.0.40
- Reduce memory footprint of errors on Rust versions 1.51+ (#145)
v1.0.39
-
Add an opt-in implementation of
Error::backtrace
on stable compilers based on thebacktrace
crate (#143)[dependencies] anyhow = { version = "1.0", features = ["backtrace"] }
v1.0.38
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
- [ ] If you want to rebase/retry this PR, check this box
This PR has been generated by Mend Renovate. View repository job log here.