rust-lang / rust-lang/rust-clippy
Add smarter way to detect if type can implement Copy
Open
Nobody has claimed this yet.
C-an-interesting-project
C-enhancement
E-hard
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
"Please implement Copy" is a suggestion that crops up in various lints. However it doesn't always make sense.
We should have some utilities that tell us:
- If the type can be
#[derive(Copy)]d - If the type can be
#![derive(Copy)]d provided all of its transitive dependencies local to this crate can be derive(copy)d (will exclude things with raw pointers)
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
Start by examining how Clippy currently handles "Please implement Copy" suggestions and identify the shared utility boundary for these lints. Define completion around detecting direct Copy derivability and transitive local dependencies, excluding types with raw pointers, with tests covering both 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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100