[stable] prepare Rust 1.93.1
This includes the following backported fixes:
- Don't try to recover keyword as non-keyword identifier rust-lang/rust#150590
- Fix `panicking_unwrap` FP on field access with implicit deref rust-lang/rust-clippy#16196
- Revert "Update wasm-related dependencies in CI" rust-lang/rust#152259
And these are just to avoid recent CI issues:
- Remove rustdoc GUI flaky test rust-lang/rust#152116
- Remove the 4 failing tests from rustdoc-gui rust-lang/rust#152194
r? @rust-lang/release
@rustbot ping relnotes-interest-group
[beta] backports
* [beta] Disable SimplifyComparisonIntegral rust-lang/rust#151267
* Use the old homu bors e-mail address again rust-lang/rust#150959
Does not backport other nominated PRs:
* Only use SSA locals in SimplifyComparisonIntegral rust-lang/rust#150925 (replaced with the disablement PR)
* Don't try to evaluate const blocks during constant promotion rust-lang/rust#150557 (backport essentially denied at this point)
* Use realstd current thread static variables in tests rust-lang/rust#150131 (as far as I can tell, this only affects internal std tests and hasn't landed in time for backport)
r? @Mark-Simulacrum
This caused several performance regressions because of existing code
which uses `Read::read` and therefore requires full buffer
initialization. This is particularly a problem when the same buffer is
re-used for multiple read calls since this means it needs to be fully
re-initialized each time.
There is still some benefit to landing the API changes, but we will have
to add private APIs so that the existing infrastructure can
track and avoid redundant initialization.
(cherry picked from commit 4b07875505)
Rollup of 11 pull requests
Successful merges:
- rust-lang/rust#148662 (alloc: Document panics when allocations will exceed max)
- rust-lang/rust#148811 (core docs: rewrite `panic::Location::caller` with visual line/column numbers)
- rust-lang/rust#149101 (Improve mutable-binding suggestion to include name)
- rust-lang/rust#149477 (float::maximum/minimum: make docs more streamlined)
- rust-lang/rust#149547 (library: Rename `IterRange*` to `Range*Iter`)
- rust-lang/rust#149548 (Generate delegation error body when delegation is not resolved)
- rust-lang/rust#149630 (Check identifiers defined in macros when suggesting identifiers hidden by hygiene)
- rust-lang/rust#149647 (Add regression test for 141845)
- rust-lang/rust#149661 (Fix for LLVM22 making lowering decisions dependent on RuntimeLibraryInfo.)
- rust-lang/rust#149666 (Add perma-unstable `--print=backend-has-zstd` for use by compiletest)
- rust-lang/rust#149671 (interpret: test SNaN handling of float min/max and update comments)
r? `@ghost`
`@rustbot` modify labels: rollup
interpret: test SNaN handling of float min/max and update comments
Also see https://github.com/rust-lang/rust/pull/149563.
I also renamed these enum variants so they are not almost identical.
Add perma-unstable `--print=backend-has-zstd` for use by compiletest
Tests for `-Zdebuginfo-compression=zstd` need to be skipped if LLVM was built without support for zstd compression.
Currently, compiletest relies on messy and fragile heuristics to detect whether the compiler's LLVM was built with zstd support. But the compiler itself already knows whether LLVM has zstd or not, so it's easier for compiletest to just ask the compiler.
---
Originally I was intending for this to be a `--print=debuginfo-compression` flag that would print out a list of values supported by `-Zdebuginfo-compression=`. I got that working locally, but it was more complex than I was happy with (in both rustc and compiletest), so I decided to cut scope and instead add a very narrow perma-unstable print request instead.
There is always a circularity hazard whenever we ask the compiler-under-test for information about how to test it. But in this case, the underlying compiler code is fairly simple, whereas the previous heuristics were inherently messy and unreliable anyway.
Add regression test for 141845
close: rust-lang/rust#141845
I saw the `tests/ui/associated-inherent-types` directory, but I felt the current location was a better fit.
Check identifiers defined in macros when suggesting identifiers hidden by hygiene
Fixrust-lang/rust#149604
r? `@JonathanBrouwer` (Since you reviewed the other one related to this)
Generate delegation error body when delegation is not resolved
This PR relates to the delegation feature rust-lang/rust#118212, it fixesrust-lang/rust#144594 ICE.
r? `@petrochenkov`
bors