miniblog.

When talking about a match or a switch statement, I've typically seen people talk about individual 'cases' or 'arms'. TIL Zig uses 'prongs' instead!

LLVM's lit tool for testing files is the most successful testing DSL I've ever seen. It's used a decent number of projects outside of LLVM. By contrast I don't see many folks using e.g. Cucumber these days.

I've never seen a good design philosophy on how to sort compiler errors for the best UX. Do you order by line, or by severity? Do you put the most actionable at the end (because that's most visible when the terminal scrolls) or at the beginning?