Re:On the Worst-Case Complexity of TimSort
by pmiller2 on Friday August 31, 2018 @03:50AM
(#17883723)
Nitpick: \rho = n/2 in the worst case, if n > 1, but that still gives you O(n log n).
[ Parent
| on HN ]
Re:On the Worst-Case Complexity of TimSort
by Fri31Aug on Friday August 31, 2018 @04:18AM
(#17883840)
Why n/2? If the array is, for example, sorted in the reverse order, then there is no monotonous run at all, in which case I believe the algorithm considers each element from the array being a run in itself, giving n runs.
Runs can be increasing or decreasing, a reversed array is a single run. Worst case is n/2 because you can always split the array in pairs (if it alternates a high and a low value for example).