-
Notifications
You must be signed in to change notification settings - Fork 1.6k
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
Tracking issue for RFC 2476, Clippy 1.0 #3343
Comments
Looks like the lint levels were changed already, i vaguely recall this happening during the rfc. Anyone want to add the version flag? |
Should the repo itself be moved to the |
I certainly wouldn't mind, but rustfmt is still on the nursery and we've
been pretty explicitly trailing behind rustfmt on such things.
cc @nrc
…On Tue, Oct 23, 2018, 9:38 AM Mazdak Farrokhzad ***@***.***> wrote:
Should the repo itself be moved to the rust-lang organization now to make
it more official?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#3343 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ABivSJkfAPtLRL07HlQNYcq0YBkH6aPtks5un0YSgaJpZM4XyA6s>
.
|
I'd be happy for the repo to move to rust-lang, but I don't see a great rush. I plan to move rustfmt at some point after the 1.0 release, probably as soon as I have time to do it. |
during such a move we could also drop the |
The repo was moved to |
This is a tracking issue for the RFC "Clippy 1.0" (rust-lang/rfcs#2476).
Steps:
shadow_unrelated
should be moved fromrestriction
topedantic
explicit_iter_loop
andexplicit_into_iter_loop
be moved fromstyle
topedantic
Unresolved questions:
None. The question of uplifts has been split out of this RFC into rust-lang/rust#53224
There isn't a "stabilization" step here per se, though we may consider moving the
clippy-preview
rustup component toclippy
cc @nrcThe text was updated successfully, but these errors were encountered: