Re: horses for courses
>>type-safe languages with optimising overrides
If that's a thing, it's a nonsense thing if 'optimising overrides' overrides type-safety. The program fails on exactly this attribute. In any case, in such an application, there's no need for extreme optimisation, (unless I'm missing something). It's a data analysis tool, in no particular hurry.
>>blaming it on the language is completely wrong.
Indeed. I'm glad we agree. C's a great language - mine of choice.
>>Something of this seriousness require belts, braces and a seriously well >>hardened bolt through the navel.
Absolutely. And more to the point, it's not system code. It is without constraints on runtime or code-size.
>>the dick-head that didn’t make sure they were up to standard that needs a >>case of manslaughter against them.
Other than for this competition, only a dick-head would write such a critical application in C. (OK, it may well be a dick-head manager insisting.)
When there's a critical safety requirement and no platform or performance constraints, C is not appropriate. Hence the firing.