rust-lang / rust-lang/rust-clippy
Lint crates that can be `#![no_std]` but aren't
Open
Nobody has claimed this yet.
A-lint
E-hard
L-unnecessary
T-middle
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
If one crate in the dependency chain depends on libstd, and only uses re-exported libcore items and/or items from other #![no_std] crates, the end result is that libstd gets pulled in even if every single other crate in the chain is #![no_std].
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no source files, tests, or entry points. Start by locating Clippy's existing lint registration and test layout, then research how dependency chains and #![no_std] usage are represented. Done means a defined lint behavior that identifies crates unnecessarily depending on libstd, with coverage for the relevant cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100