update anyhow

[RalfJung]

Fixes #100062 by incorporating dtolnay/anyhow#249

[rust-highfive]

r? @Mark-Simulacrum

(rust-highfive has picked a reviewer for you, use r? to override)

[Mark-Simulacrum]

@bors r+ rollup=iffy

[bors]

📌 Commit 2bde0e7 has been approved by Mark-Simulacrum

It is now in the queue for this repository.

[cjgillot]

Should the Cargo.lock for rustc_codegen_cranelift be updated too? cc @bjorn3

Meanwhile, this bug is a major pain to contribution.
@bors p=1

[bjorn3]

Yeah, cg_clif's Cargo.lock should probably be updated too.

[RalfJung]

When I do cargo update -p anyhow in compiler/rustc_codegen_cranelift/ it only updates to 1.0.59, to 1.0.60... no idea what's going on, I guess I better don't touch that lockfile.

[bors]

⌛ Testing commit 2bde0e7 with merge 1b57946...

[bors]

☀️ Test successful - checks-actions
Approved by: Mark-Simulacrum
Pushing 1b57946 to master...

[rust-timer]

Finished benchmarking commit (1b57946): comparison url.

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results

• Primary benchmarks: no relevant changes found
• Secondary benchmarks: mixed results

	mean1	max	count2
Regressions 😿 (primary)	N/A	N/A	0
Regressions 😿 (secondary)	3.2%	3.2%	1
Improvements 🎉 (primary)	N/A	N/A	0
Improvements 🎉 (secondary)	-2.5%	-2.7%	2
All 😿🎉 (primary)	N/A	N/A	0

Cycles

This benchmark run did not return any relevant results for this metric.

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression

Footnotes

1. the arithmetic mean of the percent change ↩

2. number of relevant changes ↩

[bjorn3]

When I do cargo update -p anyhow in compiler/rustc_codegen_cranelift/ it only updates to 1.0.59, to 1.0.60... no idea what's going on, I guess I better don't touch that lockfile.

1.0.60 has been yanked as it breaks compilation for someone: dtolnay/anyhow#250. That is why cargo didn't update it.

[RalfJung]

Ah, interesting. It is working fine here though and fixed our issue... very strange.