miniblog.

Co-Authored-By: An old Stack Overflow answer, blindly accepting the compiler's suggestions, and a linter.

Difftastic has been cited in a paper! Modernizing SMT-Based Type Error Localization https://arxiv.org/abs/2408.09034 The authors use difftastic to work out which parts of a buggy program have actually changed, a great use case :)

I'm implementing an interpreter, and wondering how often I should check for interruptions (e.g. Ctrl-C). I don't want to spend too much CPU time checking whether I've been interrupted, but I also want slow programs to stop promptly. It's tricky.