Release 1.67.1
- Revert back to LlvmArchiveBuilder on all platforms #107360
- 🚨 fix unsoundness in bootstrap cache code #105624
- Mark uninlined_format_args as pedantic rust-lang/rust-clippy#10265
- Revert "switch to the macos-12-xl builder" #107574
r? `@Mark-Simulacrum`
[beta] backport rollup
* Revert "Make nested RPITIT inherit the parent opaque's generics." #106759
* Fix mpsc::SyncSender spinning behavior #106701
* rustdoc: fix outdated lint section of the book #106605
* Do not filter substs in remap_generic_params_to_declaration_params. #106503
* Correct detection of elided lifetimes in impl-trait. #106501
* Bump rust-installer #106196
* Don't panic on stable since miri is not available there #105901
[beta] Clippy: Move manual_clamp to nursery
There was a lot of discussion about this lint in https://github.com/rust-lang/rust-clippy/pull/9484#issuecomment-1278922613
We decided to move the lint to `nursery`. But since this lint broke code of many popular projects, we don't want to wait another release cycle until this move gets into stable. So we'd like to backport this commit to `beta`.
cc `@rust-lang/clippy` for approval from the Clippy side.
[beta] backport clippy stack overflow fix
Backports https://github.com/rust-lang/rust-clippy/pull/10086 to the beta branch where the bug is still present.
I just cherry-picked the commit.
cc `@rust-lang/clippy`
This patch fixes a regression, in which `#[track_caller]`, which was
previously a no-op, was changed to actually turn on the behavior. This
should instead only happen behind the `closure_track_caller` feature
gate.
Also, add a warning for the user to understand how their code will
compile depending on the feature gate being turned on or not.
Fixes#104588
[beta] backport rollup
* Revert "Replace usage of ResumeTy in async lowering with Context" #105915
* Don't copy symbols from dylibs with -Zdylib-lto #105800
* rustdoc: Only hide lines starting with # in rust code blocks #105539
* Mangle "main" as "__main_void" on wasm32-wasi #105468
r? `@ghost`
On wasm, the age-old C trick of having a main function which can either have
no arguments or argc+argv doesn't work, because wasm requires caller and
callee signatures to match. WASI's current strategy is to have compilers
mangle main's name to indicate which signature they're using. Rust uses the
no-argument form, which should be mangled as `__main_void`.
This is needed on wasm32-wasi as of #105395.
We don't distribute a miri build for beta/stable so it needs to be kept
optional. In the future it likely makes sense to switch the miri
*artifacts* to always be built, but the rustup component to not be
included -- this will avoid some of this pain.
