Some excellent new error diagnostics from gcc with -fanalyze: https://developers.redhat.com/blog/2020/03/26/static-analysis-in-gcc-10/
The multi-function analysis reminds me of Infer, and the cute nested ASCII display resembles rustc.
Related Posts
Doing another iteration on my diagnostics display. I'm reasonably happy with the bold highlighting within the error message.
I'm not sure about the colour on Warning and Error though. It gives the output some visual structure, but arguably the message itself is more important.
I've been building an 'extract function' refactor feature. It's surprisingly nuanced.
Where do you put the extracted function? Once you've done the static analysis, what order do you use for the parameters?
Really cute approach to reporting type errors: when there's a type error, show an example of a runtime error that the type check has prevented!
Data-Driven Techniques for Type Error Diagnosis https://escholarship.org/uc/item/59s4h4pv