miniblog.

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.)

Today I learnt that `cargo fix` won't fix code with compiler errors by default, but you can override this! $ cargo fix --broken-code --allow-dirty && cargo clippy --fix --allow-dirty This incantation does exactly what I wanted :)

@tristanC That's an option! There's often cases where you know what the user wanted though, so you can provide a sensible AST that the toolchain can handle. For example, a malformed string literal can still be parsed a string so type checking etc can be helpful.