You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was looking to add a CLI extension to our very own lib https://github.com/bsm/extsort, until I stumbled across omegasort. It seems to support pretty much everything we need except that it is limited to memory and cannot operate on arbitrarily large files/streams.
Would you consider integrating extsort instead of reading all lines into memory? It should be a relatively trivial addition.
The text was updated successfully, but these errors were encountered:
This was a comment from back when omegasort was implemented in Go. This is no longer relevant.
I'm taking a look at extsort and I see one impedance that might make integrating it challenging. My code uses sort functions with the signature func(i, j int) bool. The i and j arguments are slice indexes into the data being sorted. Internally, all of the functions are operating on a []string slice.
I think the right approach would be to make the omegasort sorters work like extsort, since they're all in an internal package with no public API.
autarch
transferred this issue from houseabsolute/omegasort-go
May 6, 2023
I was looking to add a CLI extension to our very own lib https://github.com/bsm/extsort, until I stumbled across omegasort. It seems to support pretty much everything we need except that it is limited to memory and cannot operate on arbitrarily large files/streams.
Would you consider integrating extsort instead of reading all lines into memory? It should be a relatively trivial addition.
The text was updated successfully, but these errors were encountered: