rust-lang / rust-lang/rust-clippy
Catch basic array bounds errors
Open
Nobody has claimed this yet.
A-lint
E-hard
L-correctness
T-MIR
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Here:
https://www.youtube.com/watch?v=KpdSFZOQCl8&t=26m45s
They they show a PVS-Studio is able to catch statically a C++ bug similar to this:
fn foo(v: &mut [u32; 6]) {
for i in 0 ..= 6 {
v[i] += 1;
}
}
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 with the Rust example in the issue and review how Clippy currently defines and tests lints. Determine the intended diagnostics for the inclusive range indexing the six-element array, then verify that the resulting lint catches this case without inappropriate warnings.
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