Julian Gruber
Julian Gruber
no priority for me atm though, so for whoever feels like it :)
help wanted:tm: a test suite comparing multiple or all stream implementations in efficiency / performance.
co supports yielding arrays for executing in parallel, so something like this should work: ``` js var chunks = yield [ streamA(end), streamB(end), streamC(end) ] ```
Aaah didn't read you wanted to get multiple chunks per stream. Something like this:? ``` js var cat = require('co-cat'); var chunks = yield cat([ read(n, streamA), read(n, streamB), read(n,...
`yield new Error()` doesn't work with co, I don't see the advantage over throwing though
There are probably cases where this is awkward too but so far if all is pulling that's cool and if a source is pusing you can use https://github.com/segmentio/co-queue to buffer:...
what is the error you get?
The downside of this would be of course that the user can't get back to the initial value any more. But less convenient is better than not functional (in this...
+1 to not having any options in the initial implementation, with good defaults we have a useful platform for iteration
For me this far this was not a problem, as I'm using nanocomponent's implicit ID assignment for unique keys. In my understanding that `ID` is already a concept for giving...