```
$ git log --oneline 85eff7c80277b57f78b11e28d14154ab12fcf643..292f395c297d4f99171325b0842ac4ea4ff3b386
292f395c2 (HEAD) [stable 1.94] Fix symlink_and_directory when running in a long target dir name (#16777)
d00475981 Fix symlink_and_directory when running in a long target dir name (#16775)
ce98781f7 [stable 1.94] Update tar to 0.4.45 (#16769)
fec7f9297 Update tar to 0.4.45
5e256e377 Add a test for a tar file with a symlink and directory of the same name
1ed92053d test: Remove unused docker ip_address (#16636)
d7a2a0307 Increase cache_lock test timeout (#16545)
95d93fb89 Don't check the specific build-std output
dfbe729f6 chore: Updated compiler errors for Rust 1.93 (#16543)
cb03b21f6 Update cargo-semver-checks to 0.47.0
f7777c4f9 test(build-std): Update error message (#16658)
a56abe18a Disable custom target JSON spec test
634668d49 fix: `--remap-path-scope` stabilized in 1.95-nightly (#16536)
d428eaa44 fix(script): surpress `unused_features` lint for embedded (#16714)
e7b27c7f9 test(git): Mark a test as non-deterministic (#16706)
38922ca44 test(replace): Mark a test as non-deterministic (#16700)
```
Minimal backport-suitable fix to avoid returning `UNSUPPORTED_PLATFORM`
for `wasm32-wasip1-threads` which has a working pthreads implementation
via `emnapi`.
The stable regression was reported in
<https://github.com/rust-lang/rust/issues/153475>.
Assignments to a captured variable within a diverging closure should not
be considered unused if the divergence is caught.
This patch considers such assignments/captures to be used by diverging
closures irrespective of whether the divergence is caught, but better a
false negative unused lint than a false positive one (the latter having
caused a stable-to-stable regression).
(cherry picked from commit 58292e2a53)
[beta] backports, plus stable versions in stdarch
- Replace `stdarch` version placeholders with 1.94
- Parse ident with allowing recovery when trying to diagnose rust-lang/rust#151249
- Revert enabling `outline-atomics` on various platforms rust-lang/rust#151896
- Revert doc attribute parsing errors to future warnings rust-lang/rust#151952
- Remove the 4 failing tests from rustdoc-gui rust-lang/rust#152194
- Remove rustdoc GUI flaky test rust-lang/rust#152116
- Align `ArrayWindows` trait impls with `Windows` rust-lang/rust#151613
- Fix suppression of `unused_assignment` in binding of `unused_variable` rust-lang/rust#151556
- layout: handle rigid aliases without params rust-lang/rust#151814
- Fix missing unused_variables lint when using a match guard rust-lang/rust#151990
- Partially revert "resolve: Update `NameBindingData::vis` in place" rust-lang/rust#152498
- [BETA]: parse array lengths without stripping const blocks rust-lang/rust#152237
r? cuviper
Within a binding pattern match guard, only real reads of a bound local
impact its liveness analysis - not the fake read that is injected.
(cherry picked from commit 5aba6b1635)
aliases may be rigid even if they don't reference params. If the alias isn't well-formed, trying to normalize it as part of the input should have already failed
(cherry picked from commit 39a532445a)
Unused assignments to an unused variable should trigger only the
`unused_variables` lint and not also the `unused_assignments` lint.
This was previously implemented by checking whether the span of the
assignee was within the span of the binding pattern, however that failed
to capture situations was imported from elsewhere (eg from the input
tokenstream of a proc-macro that generates the binding pattern).
By comparing the span of the assignee to those of the variable
introductions instead, a reported stable-to-stable regression is
resolved.
This fix also impacted some other preexisting tests, which had
(undesirably) been triggering both the `unused_variables` and
`unused_assignments` lints on the same initializing assignment; those
tests have therefore now been updated to expect only the former lint.
(cherry picked from commit 22b3f59882)
The derived `T: Copy` constraint is not appropriate for an iterator by
reference, but we generally do not want `Copy` on iterators anyway.
(cherry picked from commit 2bae85ec52)