rust-lang/rust-clippy

`single_range_in_vec_init` should detect all kind of ranges

Closed

#16,508 opened on Feb 4, 2026

View on GitHubContributor guide
 (13 comments) (6 reactions) (1 assignee)Rust (1,391 forks)batch import
C-enhancementgood first issue

Repository metrics

Stars
 (10,406 stars)
PR merge metrics
 (Avg merge 19d 22h) (113 merged PRs in 30d)

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

Research direction
Inspect the lint implementation for `single range in vec init` in clippy lints/src/matches/range.rs. Use `clippy utils::higher::Range` to handle all range patterns (excluding `..` and `..=`). Add test cases for each range variant.
Tech stack
rust
Domain
toolingdeveloper experience
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
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.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
Rustclippy
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
60