My theory has been, that transducer stacks inline much better, hence allow
for more optimizations by the jit.
In particular I suspect that escape analysis works better on them, so the
compiler can even move some of the remaining allocations to the stack.
To verify this, try running with -verbose:g
I'm not using potemkin.
On Sunday, 8 May 2016 20:12:49 UTC-7, Alex Miller wrote:
>
> Any chance you're using an older version of potemkin? There was a bug like
> this exposed by Clojure 1.8. https://github.com/ztellman/vertigo/issues/7
--
You received this message because you are subscribed to
Any chance you're using an older version of potemkin? There was a bug like this
exposed by Clojure 1.8. https://github.com/ztellman/vertigo/issues/7
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googleg
Second update: It's the conversion from transient back to persistent that
causes the problem.
On Sunday, 8 May 2016 19:24:18 UTC-7, JvJ wrote:
>
> Update to this topic: I can create a transient cross-map, but the failure
> occurs when I call "into" on a persistent cross-map. I knew that into u
Update to this topic: I can create a transient cross-map, but the failure
occurs when I call "into" on a persistent cross-map. I knew that into used
transients internally in certain cases, but is there something that I'm
missing?
On Sunday, 8 May 2016 19:21:35 UTC-7, JvJ wrote:
>
> I'm implem
I'm implementing a data structure with persistent and transient
implementations. (Code is here:
https://github.com/JvJ/cross-map/blob/master/src/cross_map/core.cljc#L446).
When I try to convert a persistent cross-map to a transient cross-map, I
get the following exception:
ClassCastException
What?
Clojure Contrib wrapper for JDBC
https://github.com/clojure/java.jdbc#change-log
[org.clojure/java.jdbc “0.6.0-rc2”]
I had expected to go from RC 1 to Gold but the new, more consistent API offered
some opportunities for more improvements and cleaning up before we ge
In my experience, the more intermediate collections you eliminate, the more
you gain:
*Transducers:*
(criterium.core/with-progress-reporting
(criterium.core/quick-bench
(into []
(comp
(map inc))
(range 10
Execution time mean : 3.803073
I've been doing some code profiling lately, and I made one small change
that drastically improved performance.
I had this function:
(defn run-systems
"Run the systems in the order specified over
the cross-map specified."
([cm] (run-systems system-order cm))
([order cm]
(reduce (fn [a
Hi Jason,
thank for your hints, perhaps I can use your workaround.
Johannes
Am Sonntag, 8. Mai 2016 03:43:22 UTC+2 schrieb Jason Wolfe:
>
> Hi Johannes,
>
> I've run into this before. Here is a ticket [1] and some context and a
> potential workaround [2]:
>
> [1] http://dev.clojure.org/jira/b
Hi Mike!
Am Samstag, 7. Mai 2016 19:00:11 UTC+2 schrieb Mike Rodriguez:
>
> ...
> I can see how the docs @ http://clojure.org/reference/evaluation could
> mislead someone to thinking that it is perfectly fine and acceptable to
> embed any objects into a call to `eval`, but I really don't think t
I'm sure David would be happy to look at issues but it's pretty far down his
priority list these days.
--
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
Hi guys,
Seems there has been no activity on core.logic since November 2015,
Is core.logic still maintained ?
Cheers
--
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
13 matches
Mail list logo
