really cool!, I definitely have use for this. gone are the days I change,
reload repl, test :)
On Thursday, 19 November 2015 07:02:17 UTC+1, Zach Tellman wrote:
>
> It's been an uncomfortably long time since I released a new library, so
> here we go. This plugin solves a problem that has
Have a look
at
http://www.afronski.pl/sicp-in-clojure/2015/10/05/sicp-in-clojure-chapter-4.html
scroll to "Ambiguous operator",
this implements searching for combinations in a search space based on the
conditions you give it using backtracking,
also as already mentioned you could directly
from my own experience with core async I;d say yes
I've made two macros
https://github.com/gerritjvv/fun-utils/blob/master/src/fun_utils/core.clj#L208
and
https://github.com/gerritjvv/fun-utils/blob/master/src/fun_utils/core.clj#L220
that does exactly what you're referring to.
Remember if
one more thing although its unrelated to the performance differences seen:
The Character encoding specified in the Java code is US-ASCII while the
clojure reader uses UTF-8. Byte to Character encoding can make huge
differences in text processing apps see
Hi,
I do not think it has anything to do with thread sync or jit+gzip as a
matter of fact.
Why threads aren't the issue:
I've downloaded the code on my machine and the clojure code always run
slower no matter if I read one or two files, use gzip or not.
You run the test case using (future)
I agree with you that the LazySeq+Gzip+2Threads combination causing a spike
is weird.
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated -
Hi,
I'm getting the following error over and over again in my code, I've tried
adding in some print statement and suddenly the error went away and my code
worked again, then today I got the same error yet again. I suspect this
might be a race condition or something similar. I can take the same
has gone away.
On Tuesday, 7 January 2014 21:55:06 UTC+1, Gerrit Jansen van Vuuren wrote:
I do not have a single close! statement in my code anywhere. I've double
checked with grep -lhr close\! . through my whole codebase and all the
projects in it.
On Tuesday, 7 January 2014 21:05:53 UTC
