When you're writing static analysis tools, should you make your analysis flow or path dependent? What is the accuracy/performance tradeoff?
https://www.youtube.com/watch?v=JpK9e__q5Ts shows an elegant approach using monad transformers to make this pluggable.
miniblog.
Related Posts
Are there many good static analysis tools for CSS?
I have website projects in both Django and Express that almost certainly have unused rules due to unused classes.
I'm debating whether `from foo import *` is a bad feature for my toy programming language.
Forcing `import foo as f` and later `f::bar()` is so much more amenable to local static analysis. You also don't get issues with name clashes.
It's certainly convenient though.
LLMs are surprisingly good at reducing crash samples.
I've had success with "this project crashes my static analysis tool with the following command, try to shrink the repro whilst preserving the crash. Commit each smaller version to a branch".