Discuss: runTasks (plural) about piscina HOT 5 CLOSED

Yeah, I mean, I’ve thought about adding things like support for streams or async iterators, but basically my conclusion was that if you’re using async/await, you’re already doing very fine by using something along the lines of

const results = [];
for await (const task of asyncGenerator())
  results.push(await piscina.runTask(task));

from piscina.

A lot of this can be expressed through sample code or docs. The key is just illustrating the easily copyable examples of how to do it correctly and if the pattern of doing it correctly is difficult at all, a convenience API would be helpful (The streams impl might be a good example of the latter)

from piscina.

I guess the question here is: Does this actually add value or make the library easier to use? for the .all/.race/.settle variants, it’s fairly straightforward to implement those using the JS built-ins, and developers are already familiar with those anyway.

from piscina.

These would be nice to haves as far as API is concerned. If we don't do convenience APIs for these, let's illustrate how to do it correctly in the examples.

from piscina.

Closing as a nothing to do here :-)

from piscina.