Use the well known RxJS operators to manipulate arrays or iterables in a blazing fast way using the new tiny library rxjs-transducer
Most JavaScri...
For further actions, you may consider blocking this person and/or reporting abuse
Arguably,
take
is present in the form ofslice
, while the lack offirst
with an array is a non-issue. The chaining performance was already improved here: dev.to/danielescoz/improving-javas.... Using RxJS for that task is an interesting approach, though.Nice one, is this the best implementation of Transducers in TS(or even all of JS) right now, or only popular because of it's part of RxJS?
In any case, two questions:
Hi, thanks for replying. I only just created the library a few days ago, so I wouldn't say it is popular (yet) :-)
But if you have a project where you are already using RxJS and are already familiar with the operators, I think it has a low entry barrier.
new Map(transducer(xxx)(yyy))
which has a performance penalty of first allocating the array.Thanks for the feedback!
My apologies.
I assumed it was a not-even-recently-added part of the ancient RxJS behemoth.
Guess that's what I get for not clicking the I have written a transducer function link :)
I see this post was more of a camouflaged release announcement than a tutorial for an established package. 😉
I think that the line that sent me on this path the most was
Oh. I will make it more clear that this is a new library, and make it less camouflaged :-)
The first two code examples are mixed up.
It shows the transducer pipe first, then the native ES5 Array methods.
Yes, I noticed that too, but when checking the Markdown, the links to the gists are correct. Seems like a glitch in dev.to?
I created an issue here: github.com/thepracticaldev/dev.to/...
😱
This is great!