rust-lang / rust-lang/rust-clippy
Lint against unbound lifetimes
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
Following @Gankro 's blog post, we want to lint against unbound lifetimes.
The base idea is that we can collect all input lifetimes and all lifetimes contained in generics and Self. Then we check if all output lifetimes are bound by an input lifetime (either by being the same or by some 'a: 'b generic).
Once Shared/Unique become stabilized, clippy should suggest using them.
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 with the linked blog post on unbound lifetimes and compare its rules with the issue's proposed collection of input lifetimes, generic lifetimes, and Self. Done means Clippy reports unbound output lifetimes and, after Shared/Unique stabilization, suggests using them; no file or test is named in the issue.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100