I'm not sure that your iterator is async - there's no way to stop and
continue on demand. You may also try something like this
collection.asyncEach(function(err, chunk, next){
if(err) throw err
console.log(chunk)
next()
})
On Tuesday, 22 July 2014 21:11:34 UTC+4, Santiago Basulto wrote:
>
> Hello guys. I've been doning some experiments with Async iterators. You
> can find more details in the repo I created[1] but I'll explain my
> rationale behind it quickly: I'm a heavy python user and I love iterators.
> They provide a nice and clean interface. When I started to get into node.js
> I noticed the "lack" (or the lower use, to be precise) of them and started
> doing some research. The problem I found was that, for async architectures,
> blocking/regular iterators doesn't look like a good fit. Well, that's just
> something I think, maybe I'm wrong. Please share your thoughts.
>
> [1] https://github.com/santiagobasulto/async-iterators
>
--
Job board: http://jobs.nodejs.org/
New group rules:
https://gist.github.com/othiym23/9886289#file-moderation-policy-md
Old group rules:
https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
---
You received this message because you are subscribed to the Google Groups
"nodejs" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/nodejs/35643bf0-9e12-4b26-9648-c316bda312bf%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
