-
Notifications
You must be signed in to change notification settings - Fork 1.8k
Validate byte literals and byte strings #226
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
Conversation
There is something weird going on with ranges in the presence of non-ascii chars. You can try for yourself using the following literal: |
use crate::string_lexing::{ | ||
CharComponent, | ||
CharComponentKind::*, | ||
}; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Was this the indentation choice of cargo format
?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It is... Looks like a bug. I guess it will just "solve itself" when we update to a more recent version of rustfmt.
LGTM but I think we should see what the deal is with #226 (comment) before merging in case it's not #202. |
I am now certain that the wrong highlighting is caused by #202 so I am going ahead and bors r+ this |
bors r+ |
226: Validate byte literals and byte strings r=aochagavia a=aochagavia Co-authored-by: Adolfo Ochagavía <[email protected]>
Sounds good.
…On Mon, Nov 12, 2018, 10:59 AM Adolfo Ochagavía ***@***.*** wrote:
bors r+
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#226 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AEIBRKSK2wHhsMxUlTq63xpondHDSCTWks5uuZrkgaJpZM4YYp_F>
.
|
Build succeeded |
No description provided.