miniblog.

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. https://github.com/rust-lang/cc-rs/blob/main/CHANGELOG.md

The games console market is fascinating: there's incentive to *not* provide upgraded models. You want the guarantee that a game for $X just works on any $X purchased. E.g. the Switch OLED has a bigger screen, and a better CPU than the original, but it's downclocked to match the original Switch's CPU.

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.