[
https://issues.apache.org/jira/browse/LUCENE-9632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17244598#comment-17244598
]
Uwe Schindler commented on LUCENE-9632:
---------------------------------------
Actually the ArrayUtils and CollectionUtils timSort methods are not special,
they just use the Sorter interface implementation TimSorter to sort the array.
So removing them is not removing any real code, just some getters/setters for
array elements :-) If we remove them, we should also remove all other sorting
methods like introSort or others!? We won't do this because every sort
algorithm is used for different purposes in Lucene!
So I tend to keep those utility methods, as we exactly know what sort algorithm
is used and the code is tested. And we exactly know which sorting algorithm is
used when applying them. *-1* to remove.
> Replace our TimSort with JDK TimSort
> ------------------------------------
>
> Key: LUCENE-9632
> URL: https://issues.apache.org/jira/browse/LUCENE-9632
> Project: Lucene - Core
> Issue Type: Improvement
> Affects Versions: master (9.0)
> Reporter: Mike Drob
> Priority: Major
>
> JDK 11 has a TimSort with very similar lineage to our TimSort (written by
> Josh Bloch, based on Tim Peter's python list sort), we should consider
> replacing our fork with a version that we don't have to maintain.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@lucene.apache.org
For additional commands, e-mail: issues-h...@lucene.apache.org
