Skip to content

Structs/enums variant don't have a way to make an anchor in rust doc #44540

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

Closed
GuillaumeGomez opened this issue Sep 13, 2017 · 2 comments
Closed
Assignees
Labels
A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools C-feature-request Category: A feature request, i.e: not implemented / a PR. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.

Comments

@GuillaumeGomez
Copy link
Member

Currently, we have to look into the HTML directly if we want to give an anchor to a struct/enum variant. We should use the same way we do for other methods/functions/types.

Also, the generated symbol should be before, it'd allow to remove any potential issue of space we encountered recently.

cc @rust-lang/docs

@GuillaumeGomez
Copy link
Member Author

And working on it of course

@GuillaumeGomez GuillaumeGomez self-assigned this Sep 13, 2017
@GuillaumeGomez GuillaumeGomez added A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue. labels Sep 13, 2017
@Mark-Simulacrum Mark-Simulacrum added the C-feature-request Category: A feature request, i.e: not implemented / a PR. label Sep 17, 2017
@GuillaumeGomez
Copy link
Member Author

Oh it has been merged through #44661.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-docs Area: Documentation for any part of the project, including the compiler, standard library, and tools C-feature-request Category: A feature request, i.e: not implemented / a PR. T-rustdoc Relevant to the rustdoc team, which will review and decide on the PR/issue.
Projects
None yet
Development

No branches or pull requests

2 participants