Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Optional core.async helpers #55

Open
metasoarous opened this issue Mar 5, 2017 · 0 comments
Open

Optional core.async helpers #55

metasoarous opened this issue Mar 5, 2017 · 0 comments

Comments

@metasoarous
Copy link
Owner

metasoarous commented Mar 5, 2017

It would be nice to have something like slurp-async (see #54) that puts each row one by one on a go channel, perhaps using the transducers and pipeline. I don't want to make a hard requirement on core.async though, so we should follow the route of mpdairy/posh's Reagent plugin, so that the relevant function(s)/ns(s) are only defined if core.async is available. I don't know if this means a separate ns or not; Probably best not to define one unless necessary (or unless we realize there are enough such helpers that it actually makes sense to, which I doubt will be the case, since a lot of the logic gets generalized nicely with transducers).

(extracted from #45)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant