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

Occurrences of a libstd or libextra item in the tutorial and manual should link to the docs for it #623

Closed
steveklabnik opened this issue Jan 21, 2015 · 1 comment
Labels
T-doc Relevant to the documentation team, which will review and decide on the RFC.

Comments

@steveklabnik
Copy link
Member

Issue by lkuper
Monday May 27, 2013 at 04:42 GMT

For earlier discussion, see rust-lang/rust#6758

This issue was labelled with: A-rustdoc, E-hard, I-wishlist in the Rust repository


Masklinn recently suggested on rust-dev that it would be nice to have cross-linking within the generated HTML docs. E.g., an occurrence of "println" in the tutorial would be a link to here (if I understand the suggestion correctly). We could do this cross-linking for all top-level items: types, traits, functions, impls, etc.

I wouldn't expect this to happen for code blocks, just for inline code. Ideally, there would also be a way to turn it off -- both in the sense that we might want to be able to tell rustdoc not to do cross-linking on a particular run (to make the docs build faster), and in the sense that we might want to be able to specify that particular occurrences should never be cross-linked (because after a point it might hinder readability).

Presumably we'd also eventually want this cross-linking within the documentation itself, too, as well as in the tutorial and manual.

@Centril
Copy link
Contributor

Centril commented Oct 7, 2018

Closing in favor of rust-lang/rust#43466.

@Centril Centril closed this as completed Oct 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
T-doc Relevant to the documentation team, which will review and decide on the RFC.
Projects
None yet
Development

No branches or pull requests

3 participants