9 Commits

Author	SHA1	Message	Date
Michael Howell	12dc24f460	rustdoc-search: simplify rules for generics and type params ... This commit is a response to feedback on the displayed type signatures results, by making generics act stricter. Generics are tightened by making order significant. This means `Vec<Allocator>` now matches only with a true vector of allocators, instead of matching the second type param. It also makes unboxing within generics stricter, so `Result<A, B>` only matches if `B` is in the error type and `A` is in the success type. The top level of the function search is unaffected. Find the discussion on: * <https://rust-lang.zulipchat.com/#narrow/stream/393423-t-rustdoc.2Fmeetings/topic/meeting.202024-07-08/near/449965149> * <https://github.com/rust-lang/rust/pull/124544#issuecomment-2204272265> * <https://rust-lang.zulipchat.com/#narrow/channel/266220-t-rustdoc/topic/deciding.20on.20semantics.20of.20generics.20in.20rustdoc.20search/near/476841363>	2024-10-30 12:27:48 -07:00
Michael Howell	20a4b4fea1	rustdoc-search: show types signatures in results	2024-10-30 10:35:39 -07:00
Michael Howell	269cb57947	rustdoc-search: fix bugs when unboxing and reordering combine	2023-09-09 16:58:37 -07:00
Michael Howell	89a4c7f552	rustdoc: bug fix for -> option<t>	2023-09-03 13:06:07 -07:00
Michael Howell	0b3c617ec0	rustdoc-search: add support for type parameters ... When writing a type-driven search query in rustdoc, specifically one with more than one query element, non-existent types become generic parameters instead of auto-correcting (which is currently only done for single-element queries) or giving no result. You can also force a generic type parameter by writing `generic:T` (and can force it to not use a generic type parameter with something like `struct:T` or whatever, though if this happens it means the thing you're looking for doesn't exist and will give you no results). There is no syntax provided for specifying type constraints for generic type parameters. When you have a generic type parameter in a search query, it will only match up with generic type parameters in the actual function, not concrete types that match, not concrete types that implement a trait. It also strictly matches based on when they're the same or different, so `option<T>, option<U> -> option<U>` matches `Option::and`, but not `Option::or`. Similarly, `option<T>, option<T> -> option<T>`` matches `Option::or`, but not `Option::and`.	2023-09-03 13:06:06 -07:00
Michael Howell	2e569274d3	rustdoc: search for slices and arrays by type with [] ... Part of #60485	2023-06-10 13:52:54 -07:00
Guillaume Gomez	9803651ee8	Update rustdoc-js* format	2023-06-09 17:00:47 +02:00
Michael Howell	44813e038c	rustdoc: fix type search when more than one where clause applies	2023-03-07 11:37:04 -07:00
Michael Howell	9d27028391	rustdoc: function signature search with traits in where clause	2023-03-04 09:05:57 -07:00