rustdoc: Resolve some more doc links early 2

[petrochenkov]

The subset of #94857 that shouldn't be too expensive.

[rust-highfive]

r? @jsha

(rust-highfive has picked a reviewer for you, use r? to override)

[petrochenkov]

@bors try @rust-timer queue

[rust-timer]

Awaiting bors try build completion.

@rustbot label: +S-waiting-on-perf

[bors]

⌛ Trying commit 9da6155fe6c2567e87551ef74feef0497e82a6c5 with merge 26320b9f933e9393393c7362f0d75c737f4ca716...

[bors]

☀️ Try build successful - checks-actions
Build commit: 26320b9f933e9393393c7362f0d75c737f4ca716 (26320b9f933e9393393c7362f0d75c737f4ca716)

[rust-timer]

Queued 26320b9f933e9393393c7362f0d75c737f4ca716 with parent 343889b, future comparison URL.

[rust-timer]

Finished benchmarking commit (26320b9f933e9393393c7362f0d75c737f4ca716): comparison url.

Summary:

• Primary benchmarks: mixed results
• Secondary benchmarks: no relevant changes found

	Regressions 😿 (primary)	Regressions 😿 (secondary)	Improvements 🎉 (primary)	Improvements 🎉 (secondary)	All 😿 🎉 (primary)
count1	2	0	1	0	3
mean2	0.7%	N/A	-0.7%	N/A	0.2%
max	0.7%	N/A	-0.7%	N/A	0.7%

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

Benchmarking this pull request likely means that it is perf-sensitive, so we're automatically marking it as not fit for rolling up. While you can manually mark this PR as fit for rollup, we strongly recommend not doing so since this PR may lead to changes in compiler perf.

Next Steps: If you can justify the regressions found in this try perf run, please indicate this with @rustbot label: +perf-regression-triaged along with sufficient written justification. If you cannot justify the regressions please fix the regressions and do another perf run. If the next run shows neutral or positive results, the label will be automatically removed.

@bors rollup=never
@rustbot label: +S-waiting-on-review -S-waiting-on-perf +perf-regression

Footnotes

1. number of relevant changes ↩

2. the arithmetic mean of the percent change ↩

[petrochenkov]

r? @notriddle

[notriddle]

This last suggestion is a pretty minor nit. If you think the iterator version is more clear, r=me

[petrochenkov]

@bors r=notriddle

[bors]

📌 Commit 159b56f has been approved by notriddle

[bors]

⌛ Testing commit 159b56f with merge c1cfdd1...

[bors]

☀️ Test successful - checks-actions
Approved by: notriddle
Pushing c1cfdd1 to master...

[rust-timer]

Finished benchmarking commit (c1cfdd1): comparison url.

Summary:

• Primary benchmarks: mixed results
• Secondary benchmarks: no relevant changes found

	Regressions 😿 (primary)	Regressions 😿 (secondary)	Improvements 🎉 (primary)	Improvements 🎉 (secondary)	All 😿 🎉 (primary)
count1	1	0	1	0	2
mean2	0.6%	N/A	-0.9%	N/A	-0.2%
max	0.6%	N/A	-0.9%	N/A	-0.9%

If you disagree with this performance assessment, please file an issue in rust-lang/rustc-perf.

@rustbot label: -perf-regression

Footnotes

1. number of relevant changes ↩

2. the arithmetic mean of the percent change ↩