Peter Monks

@e18r good to know! I wonder if this would make a good addition to the readme?

> The single-origin policy will limit its use mostly to react-native, I'm afraid. hmmmm......yeah. Though there are several other ClojureScript runtime environments that would benefit from this being cross-platform, beyond...

@e18r not sure if it's helpful, but I got that [other library I mentioned](https://github.com/pmonks/clj-chain-reaction) enabled for cross platform builds & testing. No guarantees it's the "right" or "best" way to...

@e18r I don't, no, though [this section of the cljs-http docs](https://github.com/r0man/cljs-http#async-response-handling) seems like it might be what you're after. I don't have any experience with `core.async` either, but from the...

@e18r keeping in mind I have zero experience with `core.async`, an [atom](https://clojure.org/reference/atoms) might be the way forward here? Basically the atom would be declared outside the `go` block (e.g. in...

...JavaScript how do I hate thee? Let me count the ways... Anyhoo, I think I'm ok with that @e18r, though I'd like to see the callback interface added to both...

> I agree that, for the sake of compatibility, it makes sense to provide an asynchronous version on the Clojure side as well. However, I also believe that the synchronous...

For my use case, this issue appears when using the walk function. Basically I want to be able to walk very large directory structures (10s to 100s of millions of...

;-) Thanks for the lickety-split response - I'll keep an eye out for the update and give the new version a whirl.

Love it! Thank you for working on this!