rust-lang / rust-lang/rust-clippy

Tracking issue for RFC 2476, Clippy 1.0

Open
#3,343 6 comments 6 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue
Dominant language
Rust
Stars
13.5k
Forks
2.2k
Avg merge
2d 10h
Merged PRs (30d)
32

Description

This is a tracking issue for the RFC "Clippy 1.0" (https://github.com/rust-lang/rfcs/pull/2476).

Steps:

  • shadow_unrelated should be moved from restriction to pedantic
  • explicit_iter_loop and explicit_into_iter_loop be moved from style to pedantic
  • Add a version flag to Clippy that says 1.0
  • Update clippy_dummy published crate to 1.0

Unresolved questions:

None. The question of uplifts has been split out of this RFC into https://github.com/rust-lang/rust/issues/53224

There isn't a "stabilization" step here per se, though we may consider moving the clippy-preview rustup component to clippy cc @nrc

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading RFC 2476 and the two unchecked checklist items: adding a Clippy 1.0 version flag and updating the clippy_dummy published crate to 1.0. Locate the relevant version and publishing entry points, then verify that both checklist items are complete and that existing Clippy behavior remains intact.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
release, tooling
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.