Thus we see the gross and bizarre interaction of "Leaky Abstractions" and "Optimizations (read: Lying)". Another wonderful example of this is memory overcommit

Thus we see the gross and bizarre interaction of "Leaky Abstractions" and "Optimizations (read: Lying)". Another wonderful example of this is memory overcommitting and the OOM-killer on Linux, or the entire drama of disk caches vs power failures in just about every modern desktop and server OS, or how compiler optimizations interact with both undefined behavior and each other (especially when writing multithreaded code). My point is that this is neither new nor all that surprising. The general solution is to provide a switch to turn off the worst of the lying. I wonder how long it will take to standardize such a switch for this behavior.