miniblog.

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

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.

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