Once issue #87 and #90 are complete, abstract the sorting solution from TLKSortedList such that alternatives can be used (based on class reference on instantiation).
Presently, TLKSortedList provides a singular, internal solution for sort & search. Really, this should be abstracted in a complementing class so that alternatives can be produced, and "swapped out" by the implementing developer simply by referencing the class containing the method best suited to that implementation.
Also, this has the advantage of making it easy for developers to produce their own sort & search methods for use with TLKSortedList.
Once issue #87 and #90 are complete, abstract the sorting solution from
TLKSortedList
such that alternatives can be used (based on class reference on instantiation).Presently,
TLKSortedList
provides a singular, internal solution for sort & search. Really, this should be abstracted in a complementing class so that alternatives can be produced, and "swapped out" by the implementing developer simply by referencing the class containing the method best suited to that implementation.Also, this has the advantage of making it easy for developers to produce their own sort & search methods for use with
TLKSortedList
.