miniblog.

Thinking more about the "auto eval definitions" approach, I think it breaks down when debugging. If I want to step through the existing definition, it'd be really awkward to re-evaluate the definition at my cursor.

The lisp model of programming is generally: write a function, evaluate it, interactively call it with some arguments, iterate. Jupyter notebooks are similar. Why not automatically evaluate definitions (not expressions) whilst working? It seems like it could be a satisfying way to work with code.

Structs are great in Rust, but sometimes I find them a bit heavyweight. There's a little more syntax than e.g. OCaml, for type definitions and usages. I end up using more structs (records) in OCaml as a result. rust-analyzer has "convert tuple to named struct", which helps.