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.

In LSP, a position is represented as a line number and a column offset (in Unicode code units): https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#position This is pretty elegant. You'll get the correct line regardless of encoding bugs, and the editor already knows the line number so it's cheap to compute.

@krinkle A surprising number of PL design workarounds are "just add another equals sign" 🙃