Re:On the Worst-Case Complexity of TimSort
by sdinsn on Friday August 31, 2018 @06:16PM
(#17888927)
You are incorrect. Look at the error message more closely:
The error occurs inside TimSort, not at
It's a bug with TimSort going out of bounds (which obviously shouldn't happen ever), not the Test.
[ Parent
| on HN ]
There are no comments on this comment yet.