To any readers, if you enjoyed this article you might take a moment to check out (or checkout) iter-tools. I currently maintain it, and it provides a great toolbox for working with any kind of iterables, including Arrays, Maps, Sets and the async iterables discussed in this article. It's the only set of tools I know that won't ever leak a file handle when used with something like the FileReaderByLines class described above.
I do. Both serve the same use case, I just think iter-tools is better. A lot better actually! I've put quite a lot of my own work into it to make that be the case.
For one thing it has API docs, making it semver compliant where IxJS is not.
It also offers all its methods in both sync and async forms, which Ix does not.
I'm also fairly sure that it has vastly superior test coverage.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
To any readers, if you enjoyed this article you might take a moment to check out (or checkout) iter-tools. I currently maintain it, and it provides a great toolbox for working with any kind of iterables, including Arrays, Maps, Sets and the async iterables discussed in this article. It's the only set of tools I know that won't ever leak a file handle when used with something like the
FileReaderByLinesclass described above.Do you know IxJS?
I do. Both serve the same use case, I just think iter-tools is better. A lot better actually! I've put quite a lot of my own work into it to make that be the case.
For one thing it has API docs, making it semver compliant where IxJS is not.
It also offers all its methods in both sync and async forms, which Ix does not.
I'm also fairly sure that it has vastly superior test coverage.