-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Update comment lexing to match #198. #292
Conversation
struct NoWhitespaceAfterCommentIntroducer { | ||
static constexpr llvm::StringLiteral ShortName = "syntax-comments"; | ||
static constexpr llvm::StringLiteral Message = | ||
"Whitespace is required after '//'."; |
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.
nit: should we use markdown ` for quoting code in a message?
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.
I've asked for opinions in #toolchain, but I'd be happy with that as a convention.
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.
FWIW, I'm very supportive of generally using markdown notation in diagnostics where it fits. Markdown even has plausible nesting if/where we need it.
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.
LGTM generally. Happy for the use of ``` to land here or in a follow-up PR.
struct NoWhitespaceAfterCommentIntroducer { | ||
static constexpr llvm::StringLiteral ShortName = "syntax-comments"; | ||
static constexpr llvm::StringLiteral Message = | ||
"Whitespace is required after '//'."; |
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.
FWIW, I'm very supportive of generally using markdown notation in diagnostics where it fits. Markdown even has plausible nesting if/where we need it.
No description provided.