rust-lang / rust-lang/rust-clippy
Tracking Issue for `tuple_array_conversions`
Open
Nobody has claimed this yet.
E-help-wanted
S-needs-discussion
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Description
tuple_array_conversions was moved to nursery because of false positives. This issue tracks the FPs that need to be fixed before it can be moved back to complexity.
### Tasks
- [ ] https://github.com/rust-lang/rust-clippy/issues/11082
- [ ] https://github.com/rust-lang/rust-clippy/issues/11085
- [ ] https://github.com/rust-lang/rust-clippy/issues/11100
- [ ] https://github.com/rust-lang/rust-clippy/issues/11124
- [ ] https://github.com/rust-lang/rust-clippy/issues/11144
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 reading the five linked false-positive issues: #11082, #11085, #11100, #11124, and #11144. Use those issues to identify the affected cases and expected fixes; the tracking issue is complete when all listed tasks are resolved and tuple_array_conversions can move from nursery back to complexity.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100