rust-lang / rust-lang/rust-clippy
New lint: `shorthand_bounds` - trigger if bounds are not in a `where` clause
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
This lint allows someone to require that all bounds must be placed in a where clause.
Lint Name
shorthand_bounds
Category
restriction
Advantage
Useful for library authors to require a consistent bound style.
Drawbacks
More verbose.
Example
fn foo<T: Clone>() {}
Could be written as:
fn foo<T>()
where
T: Clone,
{}
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
No files, tests, or entry points are named in the issue. Start by locating existing restriction lints and their tests, then compare how bounds in the function signature are represented; done means a shorthand_bounds lint consistently flags bounds outside a where clause and has coverage for the shown examples.
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