pq commented 4 years ago

A good lint has a few properties that would be easy to check for statically. We should consider some tooling.

A few quick thoughts:

~ensure register* calls have corresponding visit* methods implemented~ #3426
flag uses of RecursiveAstVisitors
flag naming convention violations
warn against (certain) internal analyzer API uses
<your idea here>

(Note that some of this is currently done in the build which is great for lints in this repo but ones hosted elsewhere could benefit from similar validation.)

/fyi @bwilkerson @davidmorgan

srawlins commented 4 years ago

But who lints the linters? 😛

bwilkerson commented 4 years ago

They're self-linting.

pq commented 4 years ago

Turtles all the way down!

🐢 🐢 🐢

pq commented 2 years ago

3426 introduces a basic framework for self-checking via lints. I started with a check to ensure that we have visit methods that correspond to all node registrations.

dart-lang / linter

tooling to sanity check lints #2081

3426 introduces a basic framework for self-checking via lints. I started with a check to ensure that we have visit methods that correspond to all node registrations.