rust-lang / rust-lang/rust

Tracking issue for clippifying the standard library

Open
#161,316 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

C-tracking-issue T-libs
Dominant language
Rust
Stars
119k
Forks
16.1k
PR merge metrics
PR metrics pending

Description

This issue is to discuss and track enforcing more clippy lints in CI.

If there are specific lints you want (or conversely don't want) enabled then please mention them here.

Reminder: lints can allowed or denied at the crate or module level so we can make different decisions for core vs std or for the module that implents the thing vs everywhere else.

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 the issue discussion and reviewing how standard-library CI currently handles Clippy. Identify the proposed lints and whether they should be allowed or denied at crate or module scope. Done means the lint policy is agreed and enforcement is added to CI.

Written by the indexing model from the issue text.

Assessment

Tech stack
rust
Domain
ci-cd, tooling
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.