Escape a leading # in a doc comment #20934
Merged
Conversation
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
rustdoc was rendering this as a header
Contributor
|
r? @eddyb (rust_highfive has picked a reviewer for you, use r? to override) |
bors
referenced
this pull request
Jan 11, 2015
bors
added a commit
that referenced
this pull request
Jan 12, 2015
Escape a leading # in a doc comment Reviewed-by: eddyb
lnicola
pushed a commit
to lnicola/rust
that referenced
this pull request
Nov 4, 2025
…ntpo fix: Improve error recovery when parsing malformed function return types
lnicola
pushed a commit
to lnicola/rust
that referenced
this pull request
Nov 11, 2025
…ntpo fix: Improve error recovery when parsing malformed function return types
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
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 rendering this as a header