wants. In some
projects I expose api using inter operable with jvm abstractions like
(reactive-streams) or promises (completable future in jdk8), in other I just
use core.async.
There is no single solution I think!
My two cents!
Andrey
On Mon, Jun 1, 2015 at 9:57 PM, Alejandro Ciniglio
Zach Tellman talks about exactly this in his conj talk from last
year https://www.youtube.com/watch?v=3oQTSP4FngY
He built a library around this that essentially gives the library user a
choice of either option: https://github.com/ztellman/manifold
On Monday, June 1, 2015 at 3:18:19 PM UTC-4, C
http://www.meetup.com/Clojure-NYC/
On Friday, May 16, 2014 6:56:01 PM UTC-6, patrick lynch wrote:
>
> ...solved it - if anyone is reading this book - you're going to have to
> change your $PATH in order to get this to work.
> ...hope to see you all in the future - if anyone can recommend a Cloj
hannel after something like (>!! c [])
On Monday, April 7, 2014 1:50:18 PM UTC-4, tbc++ wrote:
>
> (async/into []) is probably the closest thing to doall
>
>
> On Mon, Apr 7, 2014 at 11:46 AM, Alejandro Ciniglio
>
> > wrote:
>
>> Sure, except you can
Sure, except you can use doall to realize the sequence from map, but there's no
equivalent for core.async.map<. I guess you could wrap it in something that
constantly tries to read from the output channel?
--
You received this message because you are subscribed to the Google
Groups "Clojure" gr
James
>
>
> On 7 April 2014 16:26, Alejandro Ciniglio
> > wrote:
>
>> Using core.async, I've understood the convention to be that if you take
>> nil from a channel, that channel is closed. This seems to hold for most
>> cases, but I've found a corner ca
Using core.async, I've understood the convention to be that if you take nil
from a channel, that channel is closed. This seems to hold for most cases,
but I've found a corner case when using map< that lets you pull nil from a
channel that is not closed.
(def a (chan))
(def c (map< seq a))
(go
Hi,
I've been using clojure for a few months now, but I've tried to avoid
writing my own macros in production code, because of the general warnings
I've heard about misusing their power and the challenges I've run into with
debugging them.
I was looking through the core.async code, and I noti
