Skip to content

Rollup of 13 pull requests - #165372

Closed
JonathanBrouwer wants to merge 202 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-WZLIsJl
Closed

JonathanBrouwer wants to merge 202 commits into
rust-lang:mainfrom
JonathanBrouwer:rollup-WZLIsJl

Conversation

@JonathanBrouwer

Copy link
Copy Markdown
Member

Successful merges:

r? @ghost

Create a similar rollup

yotamofek and others added 30 commits June 8, 2026 19:47
                                                                   Doubles the throughput on both Ice Lake and Zen4.
                                                                   Improves latency on Ice Lake from 23 to 13 cycles, on Zen4 from 17 to 15 cycles.

                                                                   Improves encoding performance of a toy base64 implementation on Zen4 by -20% (time) +25% (throughput), no change on decoding benchmark
…mals

cleanup `FlushSubnormals` implementation
Installing cargo tools (`cargo install`) without locked dependencies exposes users to supply-chain attacks to all the dependencies of the tool (https://blog.rust-lang.org/2026/08/20/supply-chain-attack-on-arrayref/). Using `cargo install --locked` reduces this risk to a compromise of the tool itself, while using the locked and hashed version of the dependencies.

I went through all `rg "cargo install"` hits in the repository and added `--locked` to all but explanatory examples (such as cargo's docs on `cargo install` itself). I validated that those tools publish functioning `Cargo.lock`s with https://gist.github.com/konstin/bcb1169c1c1120c259dca64e777a64d0.
…l-locked

Install cargo tools with locked dependencies
Use a more optimal formulation of swizzle_dyn for AVX2
See: https://github.com/actions/checkout/releases/tag/v4.4.0

This is the same version we're already implicitly using.

Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
See: https://github.com/peaceiris/actions-gh-pages/releases/tag/v3.9.3

This is the same version we're already implicitly using.

Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
See: https://github.com/taiki-e/install-action/releases/tag/v2.87.31

This is the same version we're already implicitly using. This does not
pin `cargo-nextest`, that would have to be done separately.

Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Did you know `bash` is available by default on `windows-latest` too? It
makes it much easier to write cross-platform workflows if you just use
`bash` everywhere.

Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Signed-off-by: hashcatHitman <155700084+hashcatHitman@users.noreply.github.com>
Add regression test for issue 156423

This PR adds a regression test related to issue rust-lang#156423
…, r=Mark-Simulacrum

add TrySendError::into_inner

Tracking issue: rust-lang#165102
…-cleanups, r=GuillaumeGomez

Misc. `fmt_type` cleanups

r? @GuillaumeGomez if you want it :)
…ion, r=fmease

Stop suggesting missing semicolon with multiline indexing

Making a change so that when the open bracket is on the same line as the thing being indexed, we don't suggest a semicolon. This does change some existing behaviour though:
```
foo[
  1,
  2]
```
Before, this example would recommend `foo;[` and it will now suggest `foo![` which is probably what was intended.

r? @kpreid

Closes rust-lang#161147
Add regression test for associated const equality param out of range ICE

Fixes rust-lang#145824
…res, r=fmease

Remove outdated windows-gnu test ignores
…fonthey,Urgau

Autolabel library modules

Context: this was done as part of recategorising some A-io/A-filesystem issues as A-path, which I recently created.

Essentially, we have a load of A-* labels which are explicitly just labels for library modules, but we don't autolabel PRs based upon these modules. This would be helpful for tracking work, especially for stuff like rust-lang/goals#834 which is explicitly trying to track work for `Path`.

Note that in a lot of cases I haven't fully included `sys` modules in this, but that can be improved over time. Ultimately, this is just to get a little more insight onto things, and maybe track stabilisations in release notes better.

r? nia-e

cc @rust-lang/compiler-ops since they may also care about the labels being used here
cc @workingjubilee since backtrace will be soon moved in-tree (and thus, autolabelling backtrace is nice)

----

Minor methodology note: while I think we *should* switch to using `mod.rs` more generally since it would help autolabelling, we currently don't, and so I included both the `module.rs` and `module/` patterns indiscriminately across `core`, `alloc`, and `std` under the assumption that nonexistent paths are fine to include here. I would much rather catch future changes easily if they happen than require people remembering to update this file, which, they won't. As mentioned also, the structure of `sys` could probably be improved for this, but that's a separate issue to tackle.
…econds, r=Mark-Simulacrum

Implement `Duration::display_seconds`

This implements rust-lang#165108 according to ACP rust-lang#351. (LLM are used only for spell and grammar checks.)
@rust-bors rust-bors Bot added the rollup A PR which is a rollup label Nov 2, 2026
@rustbot rustbot added A-meta Area: Issues & PRs about the rust-lang/rust repository itself A-run-make Area: port run-make Makefiles to rmake.rs A-rustdoc-json Area: Rustdoc JSON backend A-tidy Area: The tidy tool S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output. labels Nov 2, 2026
@JonathanBrouwer

Copy link
Copy Markdown
Member Author

@bors r+ p=5 force

Trying commonly failed jobs
@bors try jobs=dist-various-1,test-various,test-x86_64-gnu-aux,test-x86_64-msvc-1,test-aarch64-apple-1,test-aarch64-apple-2,test-x86_64-mingw-1,test-i686-msvc,test-armhf-gnu,test-x86_64-gnu-llvm-22-3,test-aarch64-msvc-2

@rust-bors

rust-bors Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

📌 Commit 9aab48c has been approved by JonathanBrouwer

It is now in the queue for this repository.

@rust-bors rust-bors Bot added S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. and removed S-waiting-on-review Status: Awaiting review from the assignee but also interested parties. labels Nov 2, 2026
@rust-bors

This comment has been minimized.

rust-bors Bot pushed a commit that referenced this pull request Nov 2, 2026
Rollup of 13 pull requests


try-job: dist-various-1
try-job: test-various
try-job: test-x86_64-gnu-aux
try-job: test-x86_64-msvc-1
try-job: test-aarch64-apple-1
try-job: test-aarch64-apple-2
try-job: test-x86_64-mingw-1
try-job: test-i686-msvc
try-job: test-armhf-gnu
try-job: test-x86_64-gnu-llvm-22-3
try-job: test-aarch64-msvc-2
@rust-bors rust-bors Bot added S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Nov 2, 2026
@rust-bors

rust-bors Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

This pull request was unapproved due to being closed.

@rust-bors

rust-bors Bot commented Nov 2, 2026

Copy link
Copy Markdown
Contributor

☀️ Try build successful (CI)
Build commit: e26a19d (e26a19d7b920b2b34cfff86e4cea7a2ac9db5edf)
Base parent: ae36fe2 (ae36fe22c7e590df40ffd53ac25fea35597c3f3d)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

A-meta Area: Issues & PRs about the rust-lang/rust repository itself A-run-make Area: port run-make Makefiles to rmake.rs A-rustdoc-json Area: Rustdoc JSON backend A-tidy Area: The tidy tool rollup A PR which is a rollup S-waiting-on-author Status: This is awaiting some action (such as code changes or more information) from the author. T-bootstrap Relevant to the bootstrap subteam: Rust's build system (x.py and src/bootstrap) T-compiler Relevant to the compiler team, which will review and decide on the PR/issue. T-libs Relevant to the library team, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. T-rustdoc-frontend Relevant to the rustdoc-frontend team, which will review and decide on the web UI/UX output.

Projects

None yet

Development

Successfully merging this pull request may close these issues.