rust-lang/rust-clippy

`single_range_in_vec_init` should detect all kind of ranges

Open

#16508 opened on Feb 4, 2026

View on GitHub
 (11 comments) (6 reactions) (1 assignee)Rust (10,406 stars) (1,391 forks)batch import
C-enhancementgood first issue

Description

Description

Right now, it looks like only a..b ranges are recognized. ..a, a.., and a..=b won't trigger the lint.

clippy_utils::higher::Range might be useful here.

Version

rustc 1.95.0-nightly (366a1b93e 2026-02-03)
binary: rustc
commit-hash: 366a1b93e7f466ebe559477add05f064873d0c71
commit-date: 2026-02-03
host: x86_64-unknown-linux-gnu
release: 1.95.0-nightly
LLVM version: 22.1.0

Additional Labels

No response

Contributor guide

Tech stack
rust
Domain
developer experience
Issue type
feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
blocked
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Rust AST patternsClippy lint structureclippy utils::higher::RangeClippy testing
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
35
Research direction
Locate the `single range in vec init` lint implementation in `clippy lints/src/` and study how ranges are currently matched. Examine the `clippy utils::higher::Range` helper to identify its capabilities for matching `..a`, `a..`, and `a..=b`. Review the comments on issue #16508 for any additional guidance from maintainers. Extend the pattern matching and add test cases covering all range types.