<feed xmlns='http://www.w3.org/2005/Atom'>
<title>rust/tests/rustdoc-js-std/parser-errors.js, branch 1.77.1</title>
<subtitle>https://github.com/rust-lang/rust
</subtitle>
<id>http://git.dreamy.place/mirrors/rust/atom?h=1.77.1</id>
<link rel='self' href='http://git.dreamy.place/mirrors/rust/atom?h=1.77.1'/>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/'/>
<updated>2023-12-26T19:54:17+00:00</updated>
<entry>
<title>rustdoc: search for tuples and unit by type with `()`</title>
<updated>2023-12-26T19:54:17+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-09-29T19:52:30+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=f6a045cc6b24dd033c207dd63d8adccdedf672d2'/>
<id>urn:sha1:f6a045cc6b24dd033c207dd63d8adccdedf672d2</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rustdoc-search: replace TAB/NL/LF with SP first</title>
<updated>2023-11-29T18:02:56+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-11-29T17:54:49+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=930cba8061dca5988a58b4e74774489e1b129184'/>
<id>urn:sha1:930cba8061dca5988a58b4e74774489e1b129184</id>
<content type='text'>
This way, most of the parsing code doesn't need to be designed to handle
it, since they should always be treated exactly the same anyhow.
</content>
</entry>
<entry>
<title>rustdoc-search: removed dead parser code</title>
<updated>2023-11-29T18:02:56+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-11-29T17:23:42+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=93f17117ed50a972bfabea86762241cd9ac5ccbd'/>
<id>urn:sha1:93f17117ed50a972bfabea86762241cd9ac5ccbd</id>
<content type='text'>
This is already covered by the normal unexpected char path.
</content>
</entry>
<entry>
<title>rustdoc-search: allow `:: ` and ` ::`</title>
<updated>2023-11-29T18:02:50+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-11-29T17:11:37+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=c28de27a73521c0814e771120bd0aeecde67d93b'/>
<id>urn:sha1:c28de27a73521c0814e771120bd0aeecde67d93b</id>
<content type='text'>
This restriction made sense back when spaces separated function
parameters, but now that they separate path components, there's
no real ambiguity any more.

Additionally, the Rust language allows it.
</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>Fix eBNF and handling of whitespace characters when not in a path</title>
<updated>2023-06-14T12:22:17+00:00</updated>
<author>
<name>Guillaume Gomez</name>
<email>guillaume.gomez@huawei.com</email>
</author>
<published>2023-06-13T12:01:01+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=e4ee3298656b74dd6be810862b5dd4cb8d2825b8'/>
<id>urn:sha1:e4ee3298656b74dd6be810862b5dd4cb8d2825b8</id>
<content type='text'>
</content>
</entry>
<entry>
<title>Update rustdoc-js-std tests</title>
<updated>2023-06-14T12:22:17+00:00</updated>
<author>
<name>Guillaume Gomez</name>
<email>guillaume.gomez@huawei.com</email>
</author>
<published>2023-06-12T14:05:00+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=b5f8258497d1a1a4b9d5a006e6880a3159ef6ddb'/>
<id>urn:sha1:b5f8258497d1a1a4b9d5a006e6880a3159ef6ddb</id>
<content type='text'>
</content>
</entry>
<entry>
<title>rustdoc-search: search never type with `!`</title>
<updated>2023-06-13T00:30:23+00:00</updated>
<author>
<name>Michael Howell</name>
<email>michael@notriddle.com</email>
</author>
<published>2023-06-12T21:56:54+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=db277f528407864e24d3d7934d9c23e28d950165'/>
<id>urn:sha1:db277f528407864e24d3d7934d9c23e28d950165</id>
<content type='text'>
This feature extends rustdoc to support the syntax that most users will
naturally attempt to use to search for diverging functions.
Part of #60485

It's already possible to do this search with `primitive:never`, but
that's not what the Rust language itself uses, so nobody will try it if
they aren't told or helped along.
</content>
</entry>
<entry>
<title>Update rustdoc-js* format</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:38+00:00</published>
<link rel='alternate' type='text/html' href='http://git.dreamy.place/mirrors/rust/commit/?id=9803651ee84545f8913b6fe9e76c8bd13603bb6e'/>
<id>urn:sha1:9803651ee84545f8913b6fe9e76c8bd13603bb6e</id>
<content type='text'>
</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>
</feed>
