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!

Today in cursed C code: void foo(int32_t int32_t, int32_t bar); Since C puts identifiers and typedefs in the same namespace, this code just produces a confusing compile error about the type of bar! (This occurred in some real code after macro expansion.)

Today I learnt about yamllint: if you're using YAML, you can at least ensure you're not suffering from the 'Norway problem':