rust-lang / rust-lang/rust-clippy
Lint on returning unbounded lifetimes
Open
Nobody has claimed this yet.
A-lint
E-medium
T-AST
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
http://erickt.github.io/blog/2015/09/22/if-you-use-unsafe/
If there is an output lifetime which is not bound to any input lifetimes, for a function containing unsafe, the returned lifetime can be anything up to 'static, and can be used to create pointers which live longer than their pointees.
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
The issue names no repository file, test, or entry point. Start by reading the linked article and tracing how Clippy handles lifetime relationships in unsafe functions; done means the requested lint reliably identifies output lifetimes not bound to inputs.
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
- Needs clarification
- Newbie friendliness
- 32/100