-
Notifications
You must be signed in to change notification settings - Fork 13.3k
Suggest using raw identifiers in 2018 edition when using keywords #57209
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
(rust_highfive has picked a reviewer for you, use r? to override) |
src/test/ui/editions/edition-keywords-2015-2018-expansion.stderr
Outdated
Show resolved
Hide resolved
@bors r+ |
📌 Commit 42c0f47116e34cc6ee8f52f57360f206be5c0c22 has been approved by |
⌛ Testing commit 42c0f47116e34cc6ee8f52f57360f206be5c0c22 with merge d659bcf5762178393da07258652977903e2922cb... |
💔 Test failed - status-travis |
The job Click to expand the log.
I'm a bot! I can only do what humans tell me to, so if this was not helpful or you have suggestions for improvements, please ping or otherwise contact |
@estebank |
- Suggest raw ident escaping in all editions - Keep primary label in all cases
42c0f47
to
18e0bda
Compare
@petrochenkov that sounds reasonable to me. I want to give people a chance to find out about the feature, but not to overuse it... Maybe not even using a suggestion but just linking to the book could be a good alternative. Higher barrier to finding than just accepting a change, while also having a chance to find out about them. The drawback is that I have seen people (particularly medium-experienced devs) ignoring the links even when they'd include a bit of info they wouldn't know. Maybe just an old school |
Er, I don't think too much about this. @bors r+ |
📌 Commit 18e0bda has been approved by |
Suggest using raw identifiers in 2018 edition when using keywords
☀️ Test successful - status-appveyor, status-travis |
No description provided.