rust-lang / rust-lang/rust-clippy
Redundant continue
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
Remove redundant codes
Advantage
Removed redundant codes
Drawbacks
No response
Example
fn main() {
for i in 0..5 {
dbg!(i);
continue;
}
}
Could be written as:
fn main() {
for i in 0..5 {
dbg!(i);
}
}
Comparison with existing lints
No response
Additional Context
No response
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 locating existing Rust Clippy lint implementations and their tests for redundant control-flow statements. Use the issue's examples to define the expected behavior: identify a redundant continue at the end of a loop body, ensure the lint is tested, and verify that the simplified example no longer triggers it.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100