miniblog.

Shower thought: using a tool like cargo-semver, could you build a package registry where the uploader never chooses the version number? E.g. your last release was 5.2025-09-13 and you've just changed a type, so today's release is 6.2025-11-05.

I would have thought that invoking a C compiler would be a solved problem. Looking at Rust's cc crate there's a remarkable long tail of corner cases to fix. Exotic CPUs, microarchitectures, compiler differences, operating system differences, etc.

Today I learnt that Lua projects often use *3* spaces for indentation! https://github.com/luarocks/lua-style-guide/blob/master/README.md#indentation-and-formatting I initially thought something was very wrong with editor config.