<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/src/tools/rustdoc-js, branch 1.76.0</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.76.0</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.76.0'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2023-12-15T23:26:35+00:00</updated>
<entry>
<title>rustdoc-search: remove parallel searchWords array</title>
<updated>2023-12-15T23:26:35+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-12-15T20:28:43+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=6b69ebcae0170c16e64d77939e47e3412c1637eb'/>
<id>urn:sha1:6b69ebcae0170c16e64d77939e47e3412c1637eb</id>
<content type='text'>
This might have made sense if the algorithm could use `searchWords`
to skip having to look at `searchIndex`, but since it always
does a substring check on both the stock word and the normalizedName,
it doesn't seem to help performance anyway.
</content>
</entry>
<entry>
<title>rustdoc-search: add support for associated types</title>
<updated>2023-11-20T01:54:36+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-09-23T00:27:06+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=63c50712f40055a60aefc8069661c3847bd27df4'/>
<id>urn:sha1:63c50712f40055a60aefc8069661c3847bd27df4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rustdoc: fix test case for generics that look like names</title>
<updated>2023-09-03T20:06:08+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-08-05T19:27:58+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=60688500089f8e182e35f7ae540e9941734053a4'/>
<id>urn:sha1:60688500089f8e182e35f7ae540e9941734053a4</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Change format of rustdoc-js tests by putting `query` and `correction` directly alongside the expected values</title>
<updated>2023-06-09T15:00:47+00:00</updated>
<author>
<name>Guillaume Gomez</name>
<email>guillaume.gomez@huawei.com</email>
</author>
<published>2023-06-09T14:49:19+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=6b0c7c4f01d3e6c90d10847471c7a2256346dd3e'/>
<id>urn:sha1:6b0c7c4f01d3e6c90d10847471c7a2256346dd3e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rustdoc: restructure type search engine to pick-and-use IDs</title>
<updated>2023-04-17T19:16:54+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-04-15T18:53:50+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=4c11822aebd9e9c3bbe798f14fa10ec6db3f3937'/>
<id>urn:sha1:4c11822aebd9e9c3bbe798f14fa10ec6db3f3937</id>
<content type='text'>
This change makes it so, instead of mixing string distance with
type unification, function signature search works by
mapping names to IDs at the start, reporting to the user any
cases where it had to make corrections, and then matches with
IDs when going through the items.

This only changes function searches. Name searches are left alone,
and corrections are only done when there's a single item in the
search query.
</content>
</entry>
<entry>
<title>rustdoc: add support for type filters in arguments and generics</title>
<updated>2023-03-21T05:41:57+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-03-01T01:17:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=e600c0ba0e0b8153e68c4cead3d92b2c52ca8914'/>
<id>urn:sha1:e600c0ba0e0b8153e68c4cead3d92b2c52ca8914</id>
<content type='text'>
This makes sense, since the search index has the information in it,
and it's more useful for function signature searches since a
function signature search's item type is, by definition, some type
of function (there's more than one, but not very many).
</content>
</entry>
<entry>
<title>Improve rustdoc-js tester code clarity a bit</title>
<updated>2023-03-11T20:40:17+00:00</updated>
<author>
<name>Guillaume Gomez</name>
<email>guillaume.gomez@huawei.com</email>
</author>
<published>2023-03-11T20:40:17+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=904d9c5c549745793c98a1c2cd0a2665d30fe34e'/>
<id>urn:sha1:904d9c5c549745793c98a1c2cd0a2665d30fe34e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Add eslint checks for rustdoc-js tester</title>
<updated>2023-03-11T20:37:59+00:00</updated>
<author>
<name>Guillaume Gomez</name>
<email>guillaume.gomez@huawei.com</email>
</author>
<published>2023-03-11T20:37:59+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=856c9bb481bed032f177d29288e348d6d8e060be'/>
<id>urn:sha1:856c9bb481bed032f177d29288e348d6d8e060be</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Clean up rustdoc-js tester.js file</title>
<updated>2023-03-04T20:11:34+00:00</updated>
<author>
<name>Guillaume Gomez</name>
<email>guillaume.gomez@huawei.com</email>
</author>
<published>2023-03-04T20:11:34+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=0b5165e76d2ade4b68ea4712078f7eaa1138d62e'/>
<id>urn:sha1:0b5165e76d2ade4b68ea4712078f7eaa1138d62e</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Update rustdoc-js test tool</title>
<updated>2023-03-02T11:59:04+00:00</updated>
<author>
<name>Guillaume Gomez</name>
<email>guillaume.gomez@huawei.com</email>
</author>
<published>2023-03-01T16:22:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=6b0b65424a7bc905ceed071613cbb737ed796491'/>
<id>urn:sha1:6b0b65424a7bc905ceed071613cbb737ed796491</id>
<content type='text'>
</content>
</entry>
</feed>
