Re: [ANN] Clojure 1.10 has been released!

Thanks a bunch to everyone involved. Your work is greatly appreciated! On Monday, December 17, 2018 at 12:30:01 PM UTC-5, Alex Miller wrote: > > Clojure 1.10 focuses on two major areas: improved error reporting and Java > compatibility. > > > Error reporting at the REPL now categorizes >

Re: Releasing d2q, a simple, efficient, generally applicable engine for implementing graph-pulling API servers in Clojure. Feedback wanted!

I scanned through the readme and the tutorial and I'm definitely interested to give this lib a try in my own applications. To answer your questions: - The value prop is clear an appealing, but you might want to add a comparison directly against Om-next in addition to the Pathom comparison - No c

Re: Seeking a function to partially parallelize collection processing

Thanks for these two examples, Didier. In particular, I like the second one a lot. I'm currently using a slightly altered version of my first solution that avoids batching, but the code has gotten pretty nasty. Once I get a chance I'll cleanup my solution and benchmark yours and mine and post he

Re: Seeking a function to partially parallelize collection processing

Great, I'll watch that video. Thanks again. -- 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 - please be patient with your first post. To unsu

Re: Seeking a function to partially parallelize collection processing

Thanks, Justin. Regarding the mixing of program logic with channel io, I'm don't understand why that's a problem in this case or how it could be improved. Do you mind explaining that a bit more? -- You received this message because you are subscribed to the Google Groups "Clojure" group. To pos

Re: Seeking a function to partially parallelize collection processing

Thanks for the suggestion, Didier, but I was unable to find a way to make pmap work for my use case. For those interested, here's what I came up with, then some questions: (defn parallel-per "Handle records from input-chan in parallel, but records with matching `splitter` return values seria

Re: Seeking a function to partially parallelize collection processing

Thanks Jose and Sam for the suggestions. I'm having some trouble figuring out the lifecycle for the channels created for each return value from the splitter function. I'll post my code once I have something I think works in case it's interesting to anyone in the future. -- You received this me

Re: Seeking a function to partially parallelize collection processing

Thanks Justin. My mistake. Point 2 stands. On Friday, June 16, 2017 at 3:58:38 PM UTC-4, Justin Smith wrote: > > pmap is rarely actually useful, but point 1 is false, pmap doesn't require > that it's input or output fit in memory > > On Fri, Jun 16, 2017 at 12:5

Re: Seeking a function to partially parallelize collection processing

elize the collection handling while handling subsets of the data sequentially, as I discussed in my first post. - Tom On Friday, June 16, 2017 at 10:13:11 AM UTC-4, Tom Connors wrote: > > I'm looking for a function that would likely be named something like > "sequential-by

Seeking a function to partially parallelize collection processing

I'm looking for a function that would likely be named something like "sequential-by" or "parallel-per" that takes some data-producing thing like a lazy seq or a core async channel, a function to split records from that input, and a function to handle each item. Each item with an identical retur

Re: wondering why spec.test/instrument doesn't check :ret

Thank you both for the responses and links, they've been helpful. On Saturday, August 6, 2016 at 1:02:16 PM UTC-4, Tom Connors wrote: > > spec.test/instrument doesn't check the return value of spec'd functions > and according to the spec guide this is because we should

wondering why spec.test/instrument doesn't check :ret

spec.test/instrument doesn't check the return value of spec'd functions and according to the spec guide this is because we should be checking function implementations at testing time, not development time. It seems to me that adding :ret and :fn checks to instrumented functions would be worthwhi

Re: Uberjar woes

Thanks for that tip, James - I'll look through the jars of my dependencies for spurious classes and post back here if I find anything that might be of value to future reader of this thread. On Thursday, February 27, 2014 2:49:38 PM UTC-5, Tom Connors wrote: > > Hi Everyone, > I&

Re: Uberjar woes

014 2:49:38 PM UTC-5, Tom Connors wrote: > > Hi Everyone, > I've been having trouble creating an uberjar of a project and I'm hoping > someone here can point me toward a solution. > After cleaning out the target directory (with "lein clean") and > preprocessing

Re: Uberjar woes

Hi Sam, thanks a lot for responding. Here's my project.clj: https://gist.github.com/tomconnors/9261413 On Thursday, February 27, 2014 2:49:38 PM UTC-5, Tom Connors wrote: > > Hi Everyone, > I've been having trouble creating an uberjar of a project and I'm hoping >

Uberjar woes

Hi Everyone, I've been having trouble creating an uberjar of a project and I'm hoping someone here can point me toward a solution. After cleaning out the target directory (with "lein clean") and preprocessing my cljx, I can run the project with no trouble using lein repl and lein run. I can pack