miniblog.

I've had a surprising amount of success asking an LLM to try projects in my toy programming language and report language or tooling issues. Today it noticed that foo(bar,) is syntactically legal but assert(bar,) is not. The parser error is poor in this case too. A real UX bug!

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.

Compiler error messages is such a deep topic. Even in rustc, a mature compiler that invests effort in diagnostic quality, I find interesting issues every few months. (The majority have been fixed pretty quickly, so it's really rewarding to file issues.)