How do you prevent "trusting trust" attacks with malicious compilers?
You don't need a trusted production-grade compiler. It's sufficient to have a really limited trusted compiler or even an untrusted compiler provided the triggers don't overlap.
miniblog.
Related Posts
I enjoyed this article about personal project programming, but I particularly liked this definition:
"Production code has a phone number to call when it breaks"
TIL Rust has an ambiguity `if Foo {}` -- is `Foo` a value of type bool, or a struct?
Rust solves this by defining a grammar production 'any expression except struct literals' and using it in this position.
Integration tests are inherently scary. You want to make them as similar as possible to your production environment, which massively increases the risk that one day they will talk to production directly.