rust-lang / rust-lang/rust-clippy
lints: is_deprecated, will_be_deprecated, deprecation_syntax
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
With my Deprecation RFC just accepted, we are in the unique position to be able to give clippy users more value for their deprecation annotations: We can switch the deprecation lint off and check the version in the since field (if given) against the crate version to either report is_deprecated or will_be_deprecated, or if the field doesn't contain a valid semver value, report a deprecation_syntax warning.
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 accepted Deprecation RFC and trace Clippy's existing deprecation lint handling. Implement checks for the since field against the crate version, reporting is_deprecated, will_be_deprecated, or deprecation_syntax as appropriate; done means the three lint cases are covered.
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