-
Notifications
You must be signed in to change notification settings - Fork 12.8k
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
Fix rustdoc highlighting of &
and *
#38569
Conversation
Whitespace tokens were included, so the span check used with `&` was incorrect, and it was never highlighted as kw-2. The `*` in `*foo` and `*const T` should also be highlighted kw-2, so I added them. Note that this *will* cause mishighlighting of code like `1*2`, but that should have been written `1 * 2`. Same deal with `1&2`.
(rust_highfive has picked a reviewer for you, use r? to override) |
I'm okay with this. @bors: r+ thank you! |
We'll need to be careful about this but otherwise, good job! |
@bors r=steveklabnik |
📌 Commit c9a6e87 has been approved by |
⌛ Testing commit c9a6e87 with merge c6f9d55... |
💔 Test failed - status-travis |
… On Thu, Jan 12, 2017 at 3:39 AM, bors ***@***.***> wrote:
💔 Test failed - status-travis
<https://travis-ci.org/rust-lang/rust/builds/191260197>
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#38569 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAD95EMPwhrrKsNdkYx1Rt9DAsbw_xqeks5rRhDkgaJpZM4LUnVG>
.
|
…abnik Fix rustdoc highlighting of `&` and `*` Whitespace tokens were included, so the span check used with `&` was incorrect, and it was never highlighted as kw-2 (RefKeyword). The `*` in `*foo` and `*const T` should also be highlighted kw-2, so I added them. Note that this *will* cause mishighlighting of code like `1*2`, but that should have been written `1 * 2`. Same deal with `1&2`.
☀️ Test successful - status-appveyor, status-travis |
Whitespace tokens were included, so the span check used with
&
was incorrect, and it was never highlighted as kw-2 (RefKeyword).The
*
in*foo
and*const T
should also be highlighted kw-2, so I added them. Note that this will cause mishighlighting of code like1*2
, but that should have been written1 * 2
. Same deal with1&2
.