rustdoc-search: add impl disambiguator to duplicate assoc items by notriddle · P...

Preview (to see the difference, click the link and pay attention to the specific function that comes up):

Helps with #90929

This changes the search results, specifically, when there's more than one impl with an associated item with the same name. For example, the search queries simd<i8> -> simd<i8> and simd<i64> -> simd<i64> don't link to the same function, but most of the functions have the same names.

This change should probably be FCP-ed, especially since it adds a new anchor link format for main.js to handle, so that URLs like struct.Vec.html#impl-AsMut<[T]>-for-Vec<T,+A>/method.as_mut redirect to struct.Vec.html#method.as_mut-2. It's a strange design, but there are a few reasons for it:

• I'd like to avoid making the HTML bigger. Obviously, fixing this bug is going to add at least a little more data to the search index, but adding more HTML penalises viewers for the benefit of searchers.

• Breaking struct.Vec.html#method.len would also be a disappointment.

On the other hand:

• The path-style anchors might be less prone to link rot than the numbered anchors. It's definitely less likely to have URLs that appear to "work", but silently point at the wrong thing.

• This commit arranges the path-style anchor to redirect to the numbered anchor. Nothing stops rustdoc from doing the opposite, making path-style anchors the default and redirecting the "legacy" numbered ones.

The bug

On the "Before" links, this example search calls for i64:

But if I click any of the results, I get f64 instead.

The PR fixes this problem by adding enough information to the search result href to disambiguate methods with different types but the same name.

More detailed description of the problem at:
#109422 (comment)

When a struct/enum/union has multiple impls with different type parameters, it can have multiple methods that have the same name, but which are on different impls. Besides Simd, Any also demonstrates this pattern. It has three methods named downcast, on three different impls.

When that happens, it presents a challenge in linking to the method. Normally we link like #method.foo. When there are multiple foo, we number them like #method.foo, #method.foo-1, #method.foo-2, etc.

It also presents a challenge for our search code. Currently we store all the variants in the index, but don’t have any way to generate unambiguous URLs in the results page, or to distinguish them in the SERP.

To fix this, we need three things:

1. A fragment format that fully specifies the impl type parameters when needed to disambiguate (#impl-SimdOrd-for-Simd<i64,+LANES>/method.simd_max)
2. A search index that stores methods with enough information to disambiguate the impl they were on.
3. A search results interface that can display multiple methods on the same type with the same name, when appropriate OR a disambiguation landing section on item pages?

For reviewers: it can be hard to see the new fragment format in action since it immediately gets rewritten to the numbered form.