Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Rustdoc: static methods have self argument in search-index #31598

Closed
mitaa opened this issue Feb 12, 2016 · 1 comment · Fixed by #31839
Closed

Rustdoc: static methods have self argument in search-index #31598

mitaa opened this issue Feb 12, 2016 · 1 comment · Fixed by #31839
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@mitaa
Copy link
Contributor

mitaa commented Feb 12, 2016

Searching i.e. for "vec -> vec" returns Vec::new as search result.

@steveklabnik steveklabnik added the T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. label Feb 12, 2016
@quodlibetor
Copy link
Contributor

Without the self type as the lhs of the U -> T there is no way to search for "all methods that produce T" (i.e. -> vec and similar don't work) perhaps something like * -> T and/or void -> T should be added before this is fixed?

quodlibetor added a commit to quodlibetor/rust that referenced this issue Feb 13, 2016
This enables `*` in all type positions in doc searches, which I often
want in order to find functions that create or convert specific
types (e.g. `* -> vec`) but I don't actually know what kinds of input
they expect.

I actually started working on this because of rust-lang#31598, but I've wanted it
several times when exploring new crates.
Manishearth added a commit to Manishearth/rust that referenced this issue Feb 15, 2016
…-types, r=alexcrichton

This enables `*` in all type positions in doc searches, which I often
want in order to find functions that create or convert specific
types (e.g. `* -> vec`) but I don't actually know what kinds of input
they expect.

I actually started working on this because of rust-lang#31598, but I've wanted it
several times when exploring new crates.
Manishearth pushed a commit to Manishearth/rust that referenced this issue Feb 15, 2016
This enables `*` in all type positions in doc searches, which I often
want in order to find functions that create or convert specific
types (e.g. `* -> vec`) but I don't actually know what kinds of input
they expect.

I actually started working on this because of rust-lang#31598, but I've wanted it
several times when exploring new crates.
Manishearth added a commit to Manishearth/rust that referenced this issue Feb 16, 2016
…-types, r=alexcrichton

This enables `*` in all type positions in doc searches, which I often
want in order to find functions that create or convert specific
types (e.g. `* -> vec`) but I don't actually know what kinds of input
they expect.

I actually started working on this because of rust-lang#31598, but I've wanted it
several times when exploring new crates.
bors added a commit that referenced this issue Feb 16, 2016
…lexcrichton

This enables `*` in all type positions in doc searches, which I often
want in order to find functions that create or convert specific
types (e.g. `* -> vec`) but I don't actually know what kinds of input
they expect.

I actually started working on this because of #31598, but I've wanted it
several times when exploring new crates.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants