rust-lang / rust-lang/rust-clippy
New Lints for run time analysis for raw pointer referencing
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 13.5k
- Forks
- 2.2k
- Avg merge
- 2d 10h
- Merged PRs (30d)
- 32
Description
I want to write new lints for run time Raw pointer referencing errors. But I need a mentor and detailed guidance material. Although, i have already followed and implemented This and this, but i could not found enough detailed helping material (documentation) for newcomers. For example, to analyse some rust wrong code using clippy lints. I am confused as there are lot functions/method in syntax::ast and other related crates, which function is useful for which scenario. For instance, if i want to detect that is there any unsafe or *mut or variable name “x”, so on so forth. So, how to detect this matter. I think ident.name = “unsafe” would not work.
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 doc/adding_lints.md and the linked Clippy article, then inspect the syntax::ast APIs mentioned in the issue. A complete response would give newcomers concrete guidance for identifying unsafe code, raw-pointer types, and identifiers when designing these lints, with a clear example of how to validate the approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100