miniblog.

← Back to all posts
Aug 14, 2016 at 13:11
Writing small linters using mini parsers: https://blog.acolyer.org/2016/05/31/how-to-build-static-checking-systems-using-orders-of-magnitude-less-code/ (interesting approach, but they must have corner cases)
How to build static checking systems using orders of magnitude less code
How to build static checking systems using orders of magnitude less code
How to build static checking systems using orders of magnitude less code Brown et al., ASPLOS ’16 You start with something simple. Then over time things get more and more complex and before y…

Related Posts

Dec 28, 2020 at 06:34
1
It's well known that certain compiler optimisations matter way more than others (e.g. inlining). Is there a similar principle for linters? I find red squiggles under unused/undefined variables the single most useful check.
Aug 28, 2018 at 23:23
I used to think gradual type systems (mypy, flow, typed racket) were the sweet spot. They're super-powered linters that help with refactoring, but you can run the code at any point. In a statically typed PL, you need the whole codebase to be well typed before you can run tests.
Jun 8, 2018 at 21:00
GitHub is adding an API that will allow linters to automatically fix your code for you: https://blog.github.com/changelog/2018-05-23-request-actions-on-checks/ I suppose it's the next logical step, but it will be lovely when I can apply compiler fixits from the comfort of a PR :)