I really like how clang reports type warnings that include type aliases. It's already helped me fix a bug.
miniblog.
Related Posts
I've been impressed with code written by Fable in my testing:
Difftastic: found small optimisations in a hot loop I'd already profiled extensively. Helped me prototype Dijkstra to A* too (hard to find a good heuristic).
Garden: Found some real bugs in my simplistic typechecker.
What types should you infer when code is invalid?
In Garden, + only applies to integers. What should the type of "x" + "y" be?
(1) Int: This produces cascading errors.
(2) String: We've already emitted an error anyway.
(3) Bottom.
Opinions?
I've started naming my servers digiocean1.example.com, digiocean2.example.com and so on. I wish I'd done this much earlier.
I already have domain names for the actual deployed services, but it quickly gets confusing when you start moving things around.