rust-lang / rust-lang/rust-clippy
lint redundant continue in loop
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
suggest replacing if cond { continue } <code> inside a loop with just if !cond { <code> }
Lint Name
?
Category
suspicious, complexity
Advantage
simplify code
Drawbacks
No response
Example
pub fn test(v: Vec<bool>) {
for i in v {
if !i {
continue;
}
println!("{}", i);
}
}
Could be written as:
pub fn test(v: Vec<bool>) {
for i in v {
if i {
println!("{}", i);
}
}
}
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 from the Rust examples in the issue and compare them with existing Clippy lints in the suspicious and complexity categories. No files or tests are named; a complete change would define the lint name and behavior, add the corresponding implementation and tests, and verify the suggested rewrite.
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
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100