0b3c617ec0
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`.
16 lines
352 B
Rust
16 lines
352 B
Rust
#![crate_name="foo"]
|
|
|
|
pub trait Some {}
|
|
impl Some for () {}
|
|
pub trait Other {}
|
|
impl Other for () {}
|
|
|
|
pub fn alef<T: Some>() -> T { loop {} }
|
|
pub fn alpha() -> impl Some { }
|
|
|
|
pub fn bet<T, U>(t: T) -> U { loop {} }
|
|
pub fn beta<T>(t: T) -> T {}
|
|
|
|
pub fn other<T: Other, U: Other>(t: T, u: U) { loop {} }
|
|
pub fn alternate<T: Other>(t: T, u: T) { loop {} }
|