miniblog.

I've been using "Expected Int, but got String" for my type error messages, but I've been wondering if I could do better. "Expected Int here, but this value has type String" or "This expression requires Int, but the value is String". Do you have a favourite?

I've been experimenting with different pagination UIs. It's so common to have arrows, but I've realised they're redundant here. When you have the adjacent values as well as the final value, you don't need > and >> arrows too. Thoughts?

Claude asked me a question today: was I looking for an Emacs plugin (because I was talking about elisp) or a Rust program (because I have configured Rust preferences)? I'm really impressed, it's rare to see LLMs ask follow-up questions. (I wanted Emacs in this case.)