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 links to private structs, causing 404s #23912

Closed
steveklabnik opened this issue Mar 31, 2015 · 8 comments · Fixed by #46359
Closed

rustdoc links to private structs, causing 404s #23912

steveklabnik opened this issue Mar 31, 2015 · 8 comments · Fixed by #46359
Labels
C-bug Category: This is a bug. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@steveklabnik
Copy link
Member

See http://doc.rust-lang.org/std/primitive.char.html#method.into_searcher as an example, CharEqPattern goes nowhere

@steveklabnik steveklabnik added the T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. label Mar 31, 2015
@rprichard
Copy link
Contributor

Another example: https://doc.rust-lang.org/std/fmt/struct.Formatter.html#method.align. The core::fmt::rt::v1::Alignment type is public in this case, but it's explicitly hidden.

@steveklabnik
Copy link
Member Author

Yeah, there's a lot of these.

@tomjakubowski
Copy link
Contributor

For CharEqPattern, it could be related to re-exported signatures. The same method in core doesn't have this issue: http://doc.rust-lang.org/core/primitive.char.html#method.into_searcher

Also, is it a bug that you can have private items in a public signature's QPath? Or private items in an impl for a public type? cc @alexcrichton @nikomatsakis

@tomjakubowski
Copy link
Contributor

I wonder if rustdoc should be resolving qualified paths that it encounters.

@mitaa
Copy link
Contributor

mitaa commented Apr 29, 2016

Is there still some unresolved issue here?

@steveklabnik steveklabnik added T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. and removed T-tools labels May 18, 2017
@Mark-Simulacrum Mark-Simulacrum added the C-bug Category: This is a bug. label Jul 22, 2017
@QuietMisdreavus
Copy link
Member

Still a thing; for example, Copy tries to link to types in rand, but the doc link is broken. (That link goes to 1.19.0, but it's still there in today's nightly docs.)

If i were to guess, it probably has to do with rustdoc seeing types that are in dependencies of std, but aren't being documented alongside it.

@GuillaumeGomez
Copy link
Member

Wrote a fix for it. Will make the PR tomorrow or after tomorrow.

@QuietMisdreavus
Copy link
Member

This issue was actually fixed by #44026. The issue i actually referenced in that PR was apparently a duplicate of this one. >_>

kennytm added a commit to kennytm/rust that referenced this issue Dec 20, 2017
… r=QuietMisdreavus

Do not display hidden types, fixes issue 23912

Fixes rust-lang#23912.

r? @QuietMisdreavus

(It's the one I was talking about a few days ago, just close it if it's useless.)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
C-bug Category: This is a bug. T-dev-tools Relevant to the dev-tools subteam, which will review and decide on the PR/issue. 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.

7 participants