Diagnostic for unused variables and targets
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3
- Forks
- 0
- Avg merge
- 2m
- Merged PRs (30d)
- 1
Description
It would be helpful to warn about variables that are defined but never referenced, and about non-.PHONY targets that are never used as prerequisites anywhere. Top-level entry point targets (like `all`, `install`, the default goal) would need to be excluded from this check.
Contributor guide
No contributing guide indexed for this repository
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 by locating the Makefile analysis and diagnostic entry points in the Rust LSP. Define how unused variables and non-.PHONY targets are detected while excluding top-level targets such as all, install, and the default goal; done means both diagnostics are reported with those exclusions and the relevant checks pass.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- devtools
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100