-
Notifications
You must be signed in to change notification settings - Fork 13.4k
Fix issue #666 #14631
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 issue #666 #14631
Conversation
Is it April 1st already? |
If you were serious about this, you would have put mention of it in the documentation. This also doesn’t do all of #666 inasmuch as it does not alter the pretty printer. |
Though this may not have been the world's most serious pull request, I am a On Tue, Jun 3, 2014 at 4:28 PM, Chris Morgan notifications@github.com
|
The Travis build because your PR does not define Also, if you were serious about this, #666 was rejected 2.5 years ago. |
Oh, whoops, forgot to commit one of the changes. No wonder it only works locally. |
Add new ☢ keyword for unsafe blocks
As much as I'd love to push through the reform to add a radioactive symbol to keyboards, I have a feeling we may have a hard time convincing others. I think we'll stick with the same resolution of #666 though, but perhaps we can consider this in the future! |
Perhaps we could consider feature-gating behind a lint pass, |
The `explicit_into_iter_loop`, `explicit_iter_loop` and `iter_next_loop` will now: - trigger only when the triggering expression is not located into macro code; - properly expose code rewrite proposal with code coming from the root context. changelog: [`explicit_into_iter_loop`, `explicit_iter_loop`, `iter_next_loop`]: behave in macro context Fixes rust-lang/rust-clippy#14630
Add new ☢ keyword for unsafe blocks