the basic premise is wrong: it's not a tradeoff, which would require someone to say "doing this correct and expected thing blows up because another correct and

the basic premise is wrong: it's not a tradeoff, which would require someone to say "doing this correct and expected thing blows up because another correct and expected thing can go faster". the problem is mixing in incorrect or unexpected things (like someone altering a global via a debugger). to some extent, it's fair to complain about archaic nonportabilities (such as whether dereferencing NULL will fault, or long-gone numeric representations) - the standards committees should take a deep breath and DTRT in those cases.