rust-lang / rust-lang/rust-clippy
Suggestion: Detect use of a re-export
Open
Nobody has claimed this yet.
A-lint
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
What it does
Check if something that is re-exported by the crate is used within the crate.
Advantage
The use will show the path to the actual definition and not the re-export.
Drawbacks
(Should be none.)
Example
use crate::Item;
Could be written as:
use crate::collection::Item;
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 files, tests, or entry points. Start by clarifying how the proposed check should identify an internal use of a re-export, using the crate::Item and crate::collection::Item examples. Done means the check reliably distinguishes those paths and reports the direct definition path without flagging valid imports.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100