about summary refs log tree commit diff
path: root/src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs
diff options
context:
space:
mode:
authorManish Goregaokar <manishsmail@gmail.com>2020-07-01 20:35:56 -0700
committerGitHub <noreply@github.com>2020-07-01 20:35:56 -0700
commit8d638f456ac1e1dd4c3194bb40113402377ecf85 (patch)
tree960e1335460d21e077604a0545d122fc7ebb25fe /src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs
parente04070a351f83c6ef89be5344dbcfdee2bfe7180 (diff)
parent49c1018d139746f926f1af03d1d4282e0fed7115 (diff)
downloadrust-8d638f456ac1e1dd4c3194bb40113402377ecf85.tar.gz
rust-8d638f456ac1e1dd4c3194bb40113402377ecf85.zip
Rollup merge of #73848 - pierwill:pierwill-lexer-block-doc, r=jonas-schievink
Fix markdown rendering in librustc_lexer docs

Use back-ticks instead of quotation marks in docs for the block comment variant of TokenKind.

## [Before](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_lexer/enum.TokenKind.html#variant.BlockComment) and after

<img width="1103" alt="Screen Shot 2020-06-28 at 1 22 30 PM" src="https://user-images.githubusercontent.com/19642016/85957562-446a8380-b943-11ea-913a-442cf7744083.png">

<img width="1015" alt="Screen Shot 2020-06-28 at 1 28 29 PM" src="https://user-images.githubusercontent.com/19642016/85957566-4af8fb00-b943-11ea-8fef-a09c1d586772.png">

## Question

For visual consistency, should we use back-ticks throughout the docs for these enum variants?
Diffstat (limited to 'src/test/codegen/src-hash-algorithm/src-hash-algorithm-md5.rs')
0 files changed, 0 insertions, 0 deletions