miniblog.

There are *so many* ways that reading a text file can fail. Maybe it doesn't exist, it's a broken symlink, it's actually a directory, it's not the encoding you expected, or perhaps you just don't have the correct permissions. Reporting good errors is surprisingly labour intensive.

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

An excellent review of the V language and the features it promotes: https://mawfig.github.io/2022/06/18/v-lang-in-2022.html The code samples are a great example of how you do PL work: you learn about the intended semantics and try to write programs that are broken in interesting ways.