On Thursday, October 27, 2016 at 11:39:27 AM UTC-5, Alan Thompson wrote:
>
> I almost never use either the `comp` or the `partial` functions. I think
> it is clearer to either compose the functions like Gary showed, or to use a
> threading macro (my favorite is the `it->` macro from the Tupelo l
Clojure 1.9.0-alpha14 is now available.
Try it via
- Download: https://repo1.maven.org/maven2/org/clojure/clojure/1.9.0-alpha14
- Leiningen: [org.clojure/clojure "1.9.0-alpha14"]
1.9.0-alpha14 includes the following changes since 1.9.0-alpha13:
- NEW `into` now has a 0-arity (returns []) and 1-
Hello all,
We've released (most) of the Clojure/conj 2016 speakers and program at:
http://2016.clojure-conj.org/speakers/
* Keynote - Rich Hickey
* Clojure at DataStax: The Long Road From Python to Clojure - Nick Bailey
* Barliman: Trying the Halting Problem Backwards, Blindfolded - William
Byr
That was fixed in a patch that added special cases to partial when used
with smaller numbers of arguments. It was never much slower, but it should
be just as fast as hand made functions now.
http://dev.clojure.org/jira/browse/CLJ-1430
On Fri, Oct 28, 2016 at 5:35 AM, Bobby Eickhoff wrote:
> I a
I agree that forms like (partial > 3) are clearer than #() forms. However,
I've been avoiding partial in code bases for a while -- it was measurably
slower than the alternative. Is that still the case? Has anyone else
observed slowness with partial?
On Thursday, October 27, 2016 at 8:44:14 P
