Re: Unexpected performace of transducers

Thanks Gary, Alex, Didier, I learned a lot from your replies. As per iota, I assume we're talking about this library of course . On Sun, Dec 17, 2017 at 2:40 PM, Gary Verhaegen wrote: The iota library implements a reducible object on

Re: Java 8 Lambda Interop

Sorry to awaken this old thread. It seems like reifying a valid lambda, for the specific clojure function which you want to pass to Java code, is indeed the most sensible way, given all the surface that java's lambda api entails. To the best of my knowledge no generic interop features or

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

is pretty isolated part of Clojure, so it’s basically a copy-paste job >with couple of gaps filled in that were introduced in 1.9. > > >Updating it is basically getting diff from clojure and applying it to my repo. >Sometimes with some manual corrections. > > >Nikita. &g

Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8

Nikita, this is cool, e.g. as lighttable does not yet fully support 1.9. Can you say something about how are these backports derived? so that I can get an intuition into how much it is at par with the real thing? Does it involve a lot of code rewrite to backport each 1.9 alpha version? On

Re: core.async top use cases

offs between the two though? > > > >On Monday, September 19, 2016 at 11:50:53 PM UTC-7, Matan Safriel wrote: > >Thanks but I'm not entirely sure about this. I could use agents for side >effects too, or at least I thought so. Care to further clarify? > > > Origin

Re: core.async top use cases

Thanks but I'm not entirely sure about this. I could use agents for side effects too, or at least I thought so. Care to further clarify? Original Message From:William la Forge Sent:Tue, 20 Sep 2016 02:37:20 +0300 To:Clojure

Re: core.async top use cases

>like buffering, backpressure and select aka alts. If you send an action to an >agent you don't get to know when it's done or to choose what to do if it is >currently busy.  > >On Monday, September 19, 2016 at 11:49:13 AM UTC+2, Matan Safriel wrote: > >Thanks, and I

Re: core.async top use cases

vents from any Kafka topic which also uses core.async (with an example > using Aleph and Compojure). You might like to check that repo > <https://github.com/raymcdermott/kafka-sse-clj> out too. > > Ray > > On Sunday, 18 September 2016 08:37:38 UTC+2, Matan Safriel wrote: >>

core.async top use cases

Hi, It's very easy to see how core.async solves callback hell for front-end development with clojurescript. In what use cases would you use it for server-side? we already have non-blocking IO from Java, and we have clojure agents. So what's a bunch of salient use cases? Are there prominent

Obtaining the call graph of a clojure project

Hi, Is it possible to get information about the call graph of a project from the clojure compiler? For example in Scala, one can use a compiler plugin, to tap into the AST. This in turn permits deriving more or less the entire call graph of the project, directly through the compiler, rather

Re: Handling exceptions (subject renamed)

Awesome. On Fri, Oct 5, 2012 at 8:40 PM, gaz jones gareth.e.jo...@gmail.com wrote: http://clojure.github.com/clojure/clojure.stacktrace-api.html On Fri, Oct 5, 2012 at 12:06 PM, Matt ma...@cloudaloe.org wrote: Hi, Sorry to anyone who read the original post. Apparently I had malformed