3 ms·
> something I believe the low effort tools would have caught. It's worth noting that the formal verification method brought to light the root cause, where prio
by saidajigumi 12y ago
> something I believe the low effort tools would have caught.
It's worth noting that the formal verification method brought to light the root cause, where prior attempts at fixing this bug in TimSort had merely made it less common.
Would codeSonar or PVS Studio actually have provided the insight, in "O(1)", required to fix the root cause? I'm not familiar with those tools, but I sincerely doubt it.