Prevent crash when a path is not resolved in intra-doc link

[GuillaumeGomez]

Fixes #111189.

cc @petrochenkov
r? @notriddle

[GuillaumeGomez]

So the problem was that rustfmt and clippy ident are actually specially handled by rustc and have their own Res. So ignoring these Res fixes the issue and add the needed parts into the paths queried by rustdoc.

[petrochenkov]

r? @petrochenkov
Didn't notice the ping previously.

[GuillaumeGomez]

Which is a good thing. The previous version was a lazy fix from my end. Now it's ready.

[petrochenkov]

@GuillaumeGomez
Could you use the patch from petrochenkov@721c695?
It basically does the same thing (collects some more prefixes for rustdoc diagnostics), but moves the special case from resolve_and_cache_rustdoc_path to resolve_doc_links.
@rustbot author

[GuillaumeGomez]

I applied your patch @petrochenkov.

[petrochenkov]

@bors r+

[bors]

📌 Commit bcdfda1 has been approved by petrochenkov

It is now in the queue for this repository.

[bors]

⌛ Testing commit bcdfda1 with merge d69787f...

[bors]

☀️ Test successful - checks-actions
Approved by: petrochenkov
Pushing d69787f to master...

[rust-timer]

Finished benchmarking commit (d69787f): comparison URL.

Overall result: no relevant changes - no action needed

@rustbot label: -perf-regression

Instruction count

This benchmark run did not return any relevant results for this metric.

Max RSS (memory usage)

Results

This is a less reliable metric that may be of interest but was not used to determine the overall result at the top of this comment.

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

Cycles

This benchmark run did not return any relevant results for this metric.

Binary size

This benchmark run did not return any relevant results for this metric.

Bootstrap: 647.271s -> 647.352s (0.01%)