the problem is it's kinda an anti argument you basically say if deeply unexpected things happen you prefer you program doing widely arbitrary and as such poten

the problem is it's kinda an anti argument you basically say if deeply unexpected things happen you prefer you program doing widely arbitrary and as such potentially dangerous things over it having a clean abort or proper error. ... that doesn't seem right worse it's due to a lack of the used tooling and not a fundamental problem, not only can you test this branches (using fault injection) you also often (not always) can separate them from relevant branches when collecting the branch statistics so the while argument misses the point (which is tooling is lacking, not extra checks for array bounds and similar) lastly array bounds checking is probably the worst example they could have given as it - often can be disabled/omitted in optimized builds - is quite often optimized away - has often quite low perf. overhead - bound check branches are often very easy to identify, i.e. excluding them from a 100% branch testing statistic is viable - out of bounds read/write are some of the most common cases of memory unsafety leading to security vulnerability (including full RCE cases)