Clojure are you using?
>
> This seems like a use case where transducers could help significantly in
> avoiding lazy effects and intermediate objects.
>
> On Monday, November 17, 2014 4:28:12 AM UTC-6, Alexander L. wrote:
>>
>> Hi all,
>>
>> I understand that
/transducers, which may clean
> your design. In that case, the call to reduce should be as high in
> hierarchy as possible, ideally in your top level function, with other
> functions dealing with the transformation of 'step' values.
>
> Jozef
>
> On Mon, Nov 17, 2
Hi all,
I understand that the following question is a long shot without any proper
proof/tests from my side but it's a little bit difficult to make a test
case from the specific part of my app so I will just ask anyway in case
anyone knows anything.
The situation is like this:
- I have a
Sorry for bringing this back up, but I was wondering if anyone figured out
something better...
On Saturday, September 14, 2013 10:49:08 PM UTC+3, Alexander L. wrote:
>
>
> I am developing an application and I use core.async to push data from
> multiple threads within an infinite
&g
I am developing an application and I use core.async to push data from
multiple threads within an infinite
(go (while true
> (let [data ( (do processing here...)))
in order to be processed. As you probably already figured out, I store my
channel inside an atom defined at the start of m
Hello all,
I am developing an application and I use core.async to push data from
multiple threads within an infinite
(go (while true
(let [data (http://groups.google.com/group/clojure?hl=en
---
You received this message because you are subscribed to the Google Groups
"Clojure" group.
To un
I really liked your take on this *Brian*. You kinda convinced me to use (if
(not-empty? foo)) from now on :)
Alexander
On Monday, May 27, 2013 2:58:38 AM UTC+3, Brian Marick wrote:
>
>
> On May 26, 2013, at 5:47 AM, "Alex L." >
> wrote:
> > First, the use of seq as a
> > terminating condition
