internal: make rustdoc links spiky so they are clickable#9260
Merged
bors[bot] merged 1 commit intorust-lang:masterfrom Jun 14, 2021
Merged
internal: make rustdoc links spiky so they are clickable#9260bors[bot] merged 1 commit intorust-lang:masterfrom
bors[bot] merged 1 commit intorust-lang:masterfrom
Conversation
Contributor
|
bors r+ Is not auto-linking a deliberate choice of rustdoc? Is there a an existing discussion about changing this behavior? |
Member
|
Contributor
Author
It seems like an odd choice, but there's a warning about not having auto links from the linting side of the compiler. Might be concern over ambiguity perhaps? I know that one of the bad cases of this is with parens in links, which are often seen in links to wikipedia. All I could find about it was this: rust-lang/rust#81764 |
Contributor
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Rustdoc was complaining about these while I was running with --document-private-items and I figure they should be fixed.