. It may be
worth trying out for your use-case.
On 17 Dec 2017, at 00:32, Alex Miller wrote:
On Saturday, December 16, 2017 at 2:39:14 PM UTC-6, Matan wrote:
>
> Hi,
>
> As this thread seems to have been going down this path, I am joining it
> after having spent some time fiddli
om a (self) reducible collection, and moreso why exactly?
3. Should we typically choose a different vehicle for stream processing
from large files, over using transducers? My current use case is
stream-processing from large files.
Thanks in advance for your reply,
Matan
On Tuesday,
This thread is a bit old, but it's seen two year awakenings before... and
still shows up high in google searches.
I wonder how you folks see it now. Onyx is a bit older by now, and not much
seems new out there. What would you choose for reliable and resilient
distributed computing with clojure,
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
librar
Cool!!
Sent from my mobile
Original Message
From:Nikita Prokopov
Sent:Sun, 25 Sep 2016 11:52:19 +0300
To:Clojure
Subject:Re: [ANN] clojure-future-spec, a backport of clojure.spec for 1.8
>Matan,
>
>
>spec is pretty isolated part of Clojure, so it’s basically a co
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 Wedne
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?
>
>
> Original Message
>From:William l
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
Subject:Re: core.async top use cases
>The really ni
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 put the blog post on my reading list.
>
>Althoug
ich 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:
>>
>> Hi,
>>
>&g
prominent clojure http server implementations which rely on it
for transcending the threaded web service paradigm?
Thanks,
Matan
--
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
than by picking inside the
byte code produced by the compiler.
What can be said about this aspect in Clojure?
Thanks!
Matan
--
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
Awesome.
On Fri, Oct 5, 2012 at 8:40 PM, gaz jones wrote:
> http://clojure.github.com/clojure/clojure.stacktrace-api.html
>
> On Fri, Oct 5, 2012 at 12:06 PM, Matt wrote:
> > Hi,
> >
> > Sorry to anyone who read the original post.
> > Apparently I had malformed the try block encompassing the c
13 matches
Mail list logo
