Forwarding...
-- Forwarded message --
From: Timothy Washington twash...@gmail.com
Date: Fri, Jan 3, 2014 at 1:17 PM
Subject: Re: Core.async, Rules for passing clojure vals to go block
To: Shaun Gilchrist shaunxc...@gmail.com
I'm using Prismatic's Schema in my code base. Now
for passing clojure vals to go block
To: Shaun Gilchrist shaun...@gmail.com javascript:
I'm using Prismatic's Schema in my code base. Now, it looks like defining
some functions with
s/defnhttps://github.com/Prismatic/schema/blob/master/src/clj/schema/macros.clj#L453,
yields some wonky
the
issue so I can look into it further?
Thanks!
On Friday, January 3, 2014 10:21:16 AM UTC-8, frye wrote:
Forwarding...
-- Forwarded message --
From: Timothy Washington twas...@gmail.com
Date: Fri, Jan 3, 2014 at 1:17 PM
Subject: Re: Core.async, Rules for passing clojure vals
?
Thanks!
On Friday, January 3, 2014 10:21:16 AM UTC-8, frye wrote:
Forwarding...
-- Forwarded message --
From: Timothy Washington twas...@gmail.com
Date: Fri, Jan 3, 2014 at 1:17 PM
Subject: Re: Core.async, Rules for passing clojure vals to go block
To: Shaun Gilchrist shaun
for passing clojure vals to go block
To: Shaun Gilchrist shaun...@gmail.com
I'm using Prismatic's Schema in my code base. Now, it looks like
defining some functions with
s/defnhttps://github.com/Prismatic/schema/blob/master/src/clj/schema/macros.clj#L453,
yields some wonky behaviour. Particularly
...
-- Forwarded message --
From: Timothy Washington twas...@gmail.com
Date: Fri, Jan 3, 2014 at 1:17 PM
Subject: Re: Core.async, Rules for passing clojure vals to go block
To: Shaun Gilchrist shaun...@gmail.com
I'm using Prismatic's Schema in my code base. Now, it looks like
defining some
for passing clojure vals to go block
To: Shaun Gilchrist shaun...@gmail.com
I'm using Prismatic's Schema in my code base. Now, it looks like
defining some functions with
s/defnhttps://github.com/Prismatic/schema/blob/master/src/clj/schema/macros.clj#L453,
yields some wonky behaviour. Particularly
: Timothy Washington twas...@gmail.com
Date: Fri, Jan 3, 2014 at 1:17 PM
Subject: Re: Core.async, Rules for passing clojure vals to go block
To: Shaun Gilchrist shaun...@gmail.com
I'm using Prismatic's Schema in my code base. Now, it looks like
defining some functions with
s/defnhttps
: Timothy Washington twas...@gmail.com
Date: Fri, Jan 3, 2014 at 1:17 PM
Subject: Re: Core.async, Rules for passing clojure vals to go block
To: Shaun Gilchrist shaun...@gmail.com
I'm using Prismatic's Schema in my code base. Now, it looks like
defining some functions with
s/defnhttps
: Core.async, Rules for passing clojure vals to go block
To: Shaun Gilchrist shaun...@gmail.com
I'm using Prismatic's Schema in my code base. Now, it looks like
defining some functions with
s/defnhttps://github.com/Prismatic/schema/blob/master/src/clj/schema/macros.clj#L453,
yields some
:
Forwarding...
-- Forwarded message --
From: Timothy Washington twas...@gmail.com
Date: Fri, Jan 3, 2014 at 1:17 PM
Subject: Re: Core.async, Rules for passing clojure vals to go block
To: Shaun Gilchrist shaun...@gmail.com
I'm using Prismatic's Schema in my code base. Now
Ok, got it. It was an oversight on my part. From a config file, I was
pulling in *myns/myfn*. But this is just a symbol. I needed to resolve it,
and deref the var that it pointed to. So now the below works. Tricky, but I
should have caught it earlier.
(apply @(resolve *afn*) params)
Thanks
Hi there,
For core.async, what are the rules for, *i)* having vals from a function
closure, *ii)* passed into a go block. In the example below, I cannot pass
in the system-atom to the handle function. The call will just die silently,
without throwing any exception. Instead, I have to pass in a
13 matches
Mail list logo
