Worst case performance and "impossibly unlikely" conditions
Worst case performance and "impossibly unlikely" conditions
Posted Jan 13, 2012 23:20 UTC (Fri) by rgmoore (✭ supporter ✭, #75)In reply to: Worst case performance and "impossibly unlikely" conditions by joey
Parent article: Denial of service via hash collisions
That's because they changed the default sort to merge sort, which is stable, starting in 5.8. If you want to test whether their quicksort is stable from run to run over the same data, you'd need to use sort '_quicksort'; no sort 'stable';
or the like to force it to use quicksort.