Rollup of 9 pull requests by GuillaumeGomez · Pull Request #161706 · rust-lang/rust

GuillaumeGomez · 2026-08-24T22:33:43Z

Successful merges:

bootstrap: don't LTO C dependencies on aarch64 #161689 (bootstrap: don't LTO C dependencies on aarch64)
rustdoc: fix issue preventing "read more" links from generating. #161553 (rustdoc: fix issue preventing "read more" links from generating.)
Pass LargeDataThreshold to LLVM module IR #161670 (Pass LargeDataThreshold to LLVM module IR)
rustdoc: Nuke --passes=list and defossilize the passes infrastructure #146529 (rustdoc: Nuke --passes=list and defossilize the passes infrastructure)
Check redundant_explicit_links against generated URLs #156009 (Check redundant_explicit_links against generated URLs)
Add new invalid_markdown_table rustdoc lint #159583 (Add new invalid_markdown_table rustdoc lint)
PassWrapper: handle LLVM 24 change in function types #161098 (PassWrapper: handle LLVM 24 change in function types)
Check for missing rustfmt in the stdarch intrinsic test step sooner #161641 (Check for missing rustfmt in the stdarch intrinsic test step sooner)
Don't treat slashes as path seps after drive letters in verbatim paths #161661 (Don't treat slashes as path seps after drive letters in verbatim paths)

Failed merges:

remove box_patterns #156749 (remove box_patterns)

LLVM 24 stopped using llvm::Any here to avoid heap allocations in PassInstrumentation.

Before, LargeDataThreshold was only set via `LLVMRustCreateTargetMachine`. When LTO is enabled, this information is required to be passed into the generated LLVM module IR files since the LTO linker spins up its own TargetMachine and otherwise has no knowledge of the LargeDataThreshold. Currently, `-Z large-data-threshold` has no affect at all when compiling with LTO. This commit makes sure that if `-Z large-data-threshold` is passed and not 0, it is preserved and stored into the generated LLVM IR.

… lint

The essential problem is that, with this table: ```text one | ----| a | b | c a | b | a | b a | ``` And this logic: ```rust let too_many_pipes = divider_count > expected_cells + 1; ``` `expected_cells + 1` winds up as 2, so you get this warning: ```text error: unused content after last table cell --> $DIR/invalid_markdown_table.rs:81:14 | LL | //! a | b | c | ^^^^^^ this content is discarded error: unused content after last table cell --> $DIR/invalid_markdown_table.rs:83:14 | LL | //! a | b | | ^^^^ this content is discarded error: unused content after last table cell --> $DIR/invalid_markdown_table.rs:85:14 | LL | //! a | b | ^^ this content is discarded ``` We really want our warning to give the suggest-escaping flow, like this: ```text error: table row has too many columns --> $DIR/invalid_markdown_table.rs:81:13 | LL | //! a | b | c | ^ any content after this column divider is discarded | = help: to escape `|` characters in tables, add a `\` before them like `\|` error: table row has too many columns --> $DIR/invalid_markdown_table.rs:83:13 | LL | //! a | b | | ^ any content after this column divider is discarded | = help: to escape `|` characters in tables, add a `\` before them like `\|` error: unused content after last table cell --> $DIR/invalid_markdown_table.rs:85:14 | LL | //! a | b | ^^ this content is discarded ``` By only scanning the text between the end of the last cell and the row, instead of doing the entire row, we don't have to re-implement as much of pulldown-cmark's logic.

Previously, the code unwrapped large_data_threshold with a default of 0 and sets it in the LLVM module if it is != 0. Instead, we should simply check if large_data_threshold has a value.

@Kobzol

bootstrap: don't LTO C dependencies on aarch64 Since rust-lang#161535 apparently may take a while, let's land something to un-break Miri: we know that on aarch64-linux, shipping pure-LTO object files is a bad idea as we can't assume the user has an LTO-capable linker. r? @Kobzol Cc @weihanglo

…, r=GuillaumeGomez rustdoc: fix issue preventing "read more" links from generating. fixes rust-lang#161300

…nagisa Pass LargeDataThreshold to LLVM module IR Before, LargeDataThreshold was only set via `LLVMRustCreateTargetMachine`. When LTO is enabled, this information is required to be passed into the generated LLVM module IR files since the LTO linker spins up its own TargetMachine and otherwise has no knowledge of the LargeDataThreshold. Currently, `-Z large-data-threshold` has no affect at all when compiling with LTO. This commit makes sure that if `-Z large-data-threshold` is passed and not 0, it is preserved and stored into the generated LLVM IR.

…=GuillaumeGomez rustdoc: Nuke `--passes=list` and defossilize the passes infrastructure `--passes` and `--no-defaults` were deprecated and made noops years ago except that `--passes list` still prints all passes in a human-readable format as if users could still somehow make use of that information. Removing this useless functionality allows for some small simplifications (and longer term, it would enable us to further rewrite the way we represent internal passes w/o having to worry about it possibly affecting the CLI). Given that the output of `--passes list` is *clearly* meant for human consumption only (I mean, just look at it), I hold the opinion that this removal doesn't need an FCP. And even if there were scripts somewhere out there that try to parse this output I think it would be okay to break them.

…t-links-url, r=GuillaumeGomez Check `redundant_explicit_links` against generated URLs Fixes rust-lang#155458. `rustdoc::redundant_explicit_links` checked explicit link destinations by resolving both the label and the destination as intra-doc paths. That misses links written as local rustdoc page URLs, such as `struct.B.html`, because those URLs do not appear in `doc_link_resolutions`. This PR keeps the existing path-resolution check and falls back to comparing the explicit destination with the local href that rustdoc would generate for the resolved label.

@Urgau

…able_cell, r=Urgau,notriddle,camelid Add new `invalid_markdown_table` rustdoc lint Fixes rust-lang#159186. r? @Urgau

@rustbot

…=cuviper PassWrapper: handle LLVM 24 change in function types LLVM 24 stopped using llvm::Any here [to avoid heap allocations](llvm/llvm-project@fa23198) in PassInstrumentation. @rustbot label: +llvm-main

…k-fix, r=cuviper Check for missing rustfmt in the stdarch intrinsic test step sooner Found [here](rust-lang#161422 (comment)). r? cuviper

…re, r=ChrisDenton Don't treat slashes as path seps after drive letters in verbatim paths Treat slashes as just a regular character in `\\?\C:/path\somewhere`. This mirrors how slashes are treated afterwards, e.g. in `\\?\C:\path/somewhere`, which has a component `path/somewhere`, rather than `path`, `somewhere`. Likewise, drive letters followed by `/` do not denote a `VerbatimDisk`, but an arbitrary `Verbatim` path: The prefix of `\\?\C:/path\somewhere` is `\\?\C:/path`. Fixes rust-lang#161651

GuillaumeGomez · 2026-08-24T22:33:58Z

@bors r+ p=5

rust-bors · 2026-08-24T22:34:06Z

📌 Commit 21b4ef6 has been approved by GuillaumeGomez

It is now in the queue for this repository.

rust-bors · 2026-08-25T01:40:54Z

☀️ Test successful - CI
Approved by: GuillaumeGomez
Duration: 3h 6m 22s
Pushing 9bb55c8 to main...

github-actions · 2026-08-25T01:44:08Z

What is this?

This is an experimental post-merge analysis report that shows differences in test outcomes between the merged PR and its parent PR.

Comparing e776960 (parent) -> 9bb55c8 (this PR)

Test differences

Show 15 test diffs

Stage 1

[codegen] tests/codegen-llvm/large_data_threshold.rs#DEFAULT: [missing] -> pass (J2)
[codegen] tests/codegen-llvm/large_data_threshold.rs#EXPLICIT: [missing] -> pass (J2)
[rustdoc-html] tests/rustdoc-html/trait-read-more-161300.rs: [missing] -> pass (J2)
[ui] tests/rustdoc-ui/lints/invalid_markdown_table.rs: [missing] -> pass (J2)
[codegen] tests/codegen-llvm/large_data_threshold.rs#DEFAULT: [missing] -> ignore (only executed when the architecture is x86_64) (J3)
[codegen] tests/codegen-llvm/large_data_threshold.rs#EXPLICIT: [missing] -> ignore (only executed when the architecture is x86_64) (J3)

Stage 2

[codegen] tests/codegen-llvm/large_data_threshold.rs#DEFAULT: [missing] -> pass (J0)
[codegen] tests/codegen-llvm/large_data_threshold.rs#EXPLICIT: [missing] -> pass (J0)
[codegen] tests/codegen-llvm/large_data_threshold.rs#DEFAULT: [missing] -> ignore (only executed when the architecture is x86_64) (J1)
[codegen] tests/codegen-llvm/large_data_threshold.rs#EXPLICIT: [missing] -> ignore (only executed when the architecture is x86_64) (J1)
[rustdoc-html] tests/rustdoc-html/trait-read-more-161300.rs: [missing] -> pass (J4)
[ui] tests/rustdoc-ui/lints/invalid_markdown_table.rs: [missing] -> pass (J4)
sys::path::windows::tests::test_verbatim_disk_issue_161651: [missing] -> pass (J5)

Additionally, 2 doctest diffs were found. These are ignored, as they are noisy.

Job group index

Test dashboard

Run

cargo run --manifest-path src/ci/citool/Cargo.toml -- \
    test-dashboard 9bb55c8c865411b7d9dea6ff743e583d510d89f5 --output-dir test-dashboard

And then open test-dashboard/index.html in your browser to see an overview of all executed tests.

Job duration changes

x86_64-gnu-llvm-21-2: 1h -> 1h 31m (+51.8%)
dist-i686-mingw: 1h 49m -> 2h 39m (+46.2%)
dist-i686-linux: 1h 46m -> 1h 10m (-33.9%)
i686-gnu-1: 1h 36m -> 2h 7m (+32.7%)
x86_64-gnu-llvm-21-1: 53m 52s -> 38m 45s (-28.1%)
test-various: 2h 3m -> 1h 31m (-26.2%)
x86_64-gnu-next-trait-solver-polonius: 43m 2s -> 53m 25s (+24.1%)
x86_64-msvc-1: 2h 42m -> 2h 3m (-23.7%)
dist-x86_64-msvc-alt: 2h 51m -> 2h 10m (-23.6%)
x86_64-gnu-llvm-21: 40m 1s -> 49m 21s (+23.3%)

How to interpret the job duration changes?

Job durations can vary a lot, based on the actual runner instance
that executed the job, system noise, invalidated caches, etc. The table above is provided
mostly for t-infra members, for simpler debugging of potential CI slow-downs.

rust-timer · 2026-08-25T02:24:21Z

Finished benchmarking commit (9bb55c8): comparison URL.

Overall result: ❌ regressions - please read:

Our benchmarks found a performance regression caused by this PR.
This might be an actual regression, but it can also be just noise.

Next Steps:

If the regression was expected or you think it can be justified,
please write a comment with sufficient written justification, and add
@rustbot label: +perf-regression-triaged to it, to mark the regression as triaged.
If you think that you know of a way to resolve the regression, try to create
a new PR with a fix for the regression.
If you do not understand the regression or you think that it is just noise,
you can ask the @rust-lang/wg-compiler-performance working group for help (members of this group
were already notified of this PR).

@rustbot label: +perf-regression
cc @rust-lang/wg-compiler-performance

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	0.5%	[0.5%, 0.6%]	2
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.5%	[0.5%, 0.6%]	2

Max RSS (memory usage)

Results (primary 6.7%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	6.7%	[2.7%, 10.6%]	2
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	6.7%	[2.7%, 10.6%]	2

Cycles

Results (primary -2.7%, secondary 0.2%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	3.2%	[3.2%, 3.2%]	1
Improvements ✅ (primary)	-2.7%	[-2.7%, -2.7%]	1
Improvements ✅ (secondary)	-2.7%	[-2.7%, -2.7%]	1
All ❌✅ (primary)	-2.7%	[-2.7%, -2.7%]	1

Binary size

This perf run didn't have relevant results for this metric.

Bootstrap: 471.419s -> 476.471s (1.07%)
Artifact size: 400.34 MiB -> 400.96 MiB (0.16%)

rust-bors · 2026-08-25T02:47:37Z

📌 Perf builds for each rolled up PR:

PR#	Message	Perf Build Sha
#161689	bootstrap: don't LTO C dependencies on aarch64	`89d9a83de62eb9f0a01a1b1a5b83e3e246f26285` (link)
#161553	rustdoc: fix issue preventing "read more" links from genera…	`589a9c5d23f118f38e0599549caf701590986bd0` (link)
#161670	Pass LargeDataThreshold to LLVM module IR	`9e74e414d5f8a446e6dcb42fd968116ec87c0a74` (link)
#146529	rustdoc: Nuke `--passes=list` and defossilize the passes in…	`51502e86ac48af8f9f53795845b470259817622a` (link)
#156009	Check `redundant_explicit_links` against generated URLs	`823287b65dd11740d03568285145ba144f950b23` (link)
#159583	Add new `invalid_markdown_table` rustdoc lint	`ff4bc60fc43dcc2cbeca3d74f550a920e95ec641` (link)
#161098	PassWrapper: handle LLVM 24 change in function types	`db040b543c43d704354ffd1c196ef9e78dab3fa2` (link)
#161641	Check for missing rustfmt in the stdarch intrinsic test ste…	`33e5e74229f0bc41bd0addbd5a5b9f9e88bc9779` (link)
#161661	Don't treat slashes as path seps after drive letters in ver…	`745a7e5d682ad5f015fb4e77f1af4b5b9882706c` (link)

parent commit: e7769602ac

In the case of a perf regression, run the following command for each PR you suspect might be the cause: @rust-timer build $SHA

JonathanBrouwer · 2026-08-25T06:46:24Z

@rust-timer triage 51502e8 823287b ff4bc60

rust-timer · 2026-08-25T06:46:29Z

#146529 `51502e8` rustdoc: Nuke `--passes=list` and defossilize the passes infrastructure

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary 7.2%, secondary 5.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	7.2%	[7.2%, 7.2%]	1
Regressions ❌ (secondary)	5.3%	[5.3%, 5.3%]	1
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	7.2%	[7.2%, 7.2%]	1

Cycles

Results (primary -3.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-3.0%	[-3.0%, -3.0%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-3.0%	[-3.0%, -3.0%]	1

Binary size

Results (primary -0.1%, secondary -0.1%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-0.1%	[-0.2%, -0.0%]	79
Improvements ✅ (secondary)	-0.1%	[-0.2%, -0.0%]	66
All ❌✅ (primary)	-0.1%	[-0.2%, -0.0%]	79

#156009 `823287b` Check `redundant_explicit_links` against generated URLs

Instruction count

This perf run didn't have relevant results for this metric.

Max RSS (memory usage)

Results (primary -0.4%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	2.8%	[2.8%, 2.8%]	1
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-3.7%	[-3.7%, -3.7%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-0.4%	[-3.7%, 2.8%]	2

Cycles

Results (primary -3.5%, secondary 17.5%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	17.5%	[17.5%, 17.5%]	1
Improvements ✅ (primary)	-3.5%	[-3.5%, -3.5%]	1
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	-3.5%	[-3.5%, -3.5%]	1

Binary size

Results (primary -0.0%, secondary -0.0%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-0.0%	[-0.0%, -0.0%]	4
Improvements ✅ (secondary)	-0.0%	[-0.0%, -0.0%]	2
All ❌✅ (primary)	-0.0%	[-0.0%, -0.0%]	4

#159583 `ff4bc60` Add new `invalid_markdown_table` rustdoc lint

Instruction count

Our most reliable metric. Used to determine the overall result above. However, even this metric can be noisy.

	mean	range	count
Regressions ❌ (primary)	0.5%	[0.5%, 0.6%]	2
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	0.5%	[0.5%, 0.6%]	2

Max RSS (memory usage)

Results (primary 7.8%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	7.8%	[7.8%, 7.8%]	1
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-	-	0
Improvements ✅ (secondary)	-	-	0
All ❌✅ (primary)	7.8%	[7.8%, 7.8%]	1

Cycles

Results (primary -2.9%, secondary -2.3%)

A less reliable metric. May be of interest, but not used to determine the overall result above.

	mean	range	count
Regressions ❌ (primary)	-	-	0
Regressions ❌ (secondary)	-	-	0
Improvements ✅ (primary)	-2.9%	[-2.9%, -2.9%]	1
Improvements ✅ (secondary)	-2.3%	[-2.3%, -2.3%]	1
All ❌✅ (primary)	-2.9%	[-2.9%, -2.9%]	1

Binary size

This perf run didn't have relevant results for this metric.

JonathanBrouwer · 2026-08-25T08:56:37Z

Caused by #159583
@rustbot label: +perf-regression-triaged

durin42 and others added 28 commits August 14, 2026 10:53

PassWrapper: handle LLVM 24 change in function types

299213f

LLVM 24 stopped using llvm::Any here to avoid heap allocations in PassInstrumentation.

PassWrapper: clang-format

50b867f

Check for missing rustfmt in the stdarch intrinsic test step sooner

226b175

Don't treat slashes as path seps after drive letters in verbatim paths

afcb367

Add new unescaped_pipe_in_table_cell rustdoc lint

97967de

Add ui regression test for new rustdoc unescaped_pipe_in_table_cell…

dbe2c8e

… lint

Add documentation for rustdoc unescaped_pipe_in_table_cell lint

f74d66c

Rename lint unescaped_pipe_in_table_cell into invalid_markdown_table

fe90bb2

Also warn in case there is content after the last table cell

67bfe3a

Update lint to new rustdoc table lint

aeb0d4a

Fix whitespace.

1f7f241

rustdoc: fix issue preventing "read more" links from generating.

eb1aebf

rustdoc: Nuke --passes=list

a83329a

rustdoc: Defossilize the passes infrastructure

f1acecf

bootstrap: don't LTO C dependencies on aarch64

b1f7d8e

rustdoc: check redundant explicit links against generated URLs

1f5e36d

Simply check if the large_data_threshold is set instead of unwrapping

e6bae81

Previously, the code unwrapped large_data_threshold with a default of 0 and sets it in the LLVM module if it is != 0. Instead, we should simply check if large_data_threshold has a value.

Rollup merge of rust-lang#161553 - lolbinarycat:rustdoc-fix-read-more…

7d749cf

…, r=GuillaumeGomez rustdoc: fix issue preventing "read more" links from generating. fixes rust-lang#161300

Rollup merge of rust-lang#159583 - GuillaumeGomez:unescaped_pipe_in_t…

3e5db1a

…able_cell, r=Urgau,notriddle,camelid Add new `invalid_markdown_table` rustdoc lint Fixes rust-lang#159186. r? @Urgau

Rollup merge of rust-lang#161098 - durin42:llvm-24-llvm-any-change, r…

4de5370

…=cuviper PassWrapper: handle LLVM 24 change in function types LLVM 24 stopped using llvm::Any here [to avoid heap allocations](llvm/llvm-project@fa23198) in PassInstrumentation. @rustbot label: +llvm-main

Rollup merge of rust-lang#161641 - Kobzol:intrinsic-test-rustfmt-chec…

a7026e0

…k-fix, r=cuviper Check for missing rustfmt in the stdarch intrinsic test step sooner Found [here](rust-lang#161422 (comment)). r? cuviper

rust-bors Bot added the rollup A PR which is a rollup label Aug 24, 2026

rustbot added the A-LLVM Area: Code generation parts specific to LLVM. Both correctness bugs and optimization-related issues. label Aug 24, 2026

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 Aug 24, 2026

GuillaumeGomez mentioned this pull request Aug 24, 2026

bootstrap: don't LTO C dependencies on aarch64 #161689

Merged

This comment has been minimized.

Sign in to view

rust-bors Bot added merged-by-bors This PR was explicitly merged by bors. and removed S-waiting-on-bors Status: Waiting on bors to run and complete tests. Bors will change the label on completion. labels Aug 25, 2026

rust-bors Bot merged commit 9bb55c8 into rust-lang:main Aug 25, 2026
14 checks passed

rustbot added this to the 1.100.0 milestone Aug 25, 2026

rust-bors Bot mentioned this pull request Aug 25, 2026

Lint useless or-pattern alternatives under unreachable_patterns #161613

Draft

rustbot added the perf-regression Performance regression. label Aug 25, 2026

rustbot added the perf-regression-triaged The performance regression has been triaged. label Aug 25, 2026

GuillaumeGomez deleted the rollup-UfytneT branch August 25, 2026 09:39

Navigation Menu

Uh oh!

Uh oh!

Rollup of 9 pull requests - #161706

Rollup of 9 pull requests#161706
rust-bors[bot] merged 28 commits into
rust-lang:mainfrom
GuillaumeGomez:rollup-UfytneT

GuillaumeGomez commented Aug 24, 2026

Uh oh!

GuillaumeGomez commented Aug 24, 2026

Uh oh!

rust-bors Bot commented Aug 24, 2026

Uh oh!

This comment has been minimized.

rust-bors Bot commented Aug 25, 2026

Uh oh!

Uh oh!

github-actions Bot commented Aug 25, 2026

Stage 1

Stage 2

Uh oh!

rust-timer commented Aug 25, 2026

Uh oh!

rust-bors Bot commented Aug 25, 2026

Uh oh!

JonathanBrouwer commented Aug 25, 2026

Uh oh!

rust-timer commented Aug 25, 2026 •

edited

Loading

Uh oh!

JonathanBrouwer commented Aug 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

13 participants

Uh oh!

Uh oh!

Conversation

GuillaumeGomez commented Aug 24, 2026

Uh oh!

GuillaumeGomez commented Aug 24, 2026

Uh oh!

rust-bors Bot commented Aug 24, 2026

Uh oh!

This comment has been minimized.

rust-bors Bot commented Aug 25, 2026

Uh oh!

Uh oh!

github-actions Bot commented Aug 25, 2026

Test differences

Stage 1

Stage 2

Job duration changes

Uh oh!

rust-timer commented Aug 25, 2026

Overall result: ❌ regressions - please read:

Uh oh!

rust-bors Bot commented Aug 25, 2026

Uh oh!

JonathanBrouwer commented Aug 25, 2026

Uh oh!

rust-timer commented Aug 25, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

#146529 51502e8 rustdoc: Nuke --passes=list and defossilize the passes infrastructure

#156009 823287b Check redundant_explicit_links against generated URLs

#159583 ff4bc60 Add new invalid_markdown_table rustdoc lint

Uh oh!

JonathanBrouwer commented Aug 25, 2026

Uh oh!

Reviewers

Assignees

Labels

Projects

Milestone

Development

Uh oh!

13 participants

rust-timer commented Aug 25, 2026 •

edited

Loading

#146529 `51502e8` rustdoc: Nuke `--passes=list` and defossilize the passes infrastructure

#156009 `823287b` Check `redundant_explicit_links` against generated URLs

#159583 `ff4bc60` Add new `invalid_markdown_table` rustdoc lint