Re: Feedback on idiomatic API design

On Wed, Mar 9, 2016 at 6:20 AM, Johan Haleby wrote: > Thanks for your feedback, exactly what I wanted. > > On Tuesday, March 8, 2016 at 3:16:02 PM UTC+1, mlimotte wrote: >> >> I don't think you need a macro here. In any case, I'd avoid using a >> macro as late as possible. See how far you get w

Re: Feedback on idiomatic API design

Thanks for your feedback, exactly what I wanted. On Tuesday, March 8, 2016 at 3:16:02 PM UTC+1, mlimotte wrote: > > I don't think you need a macro here. In any case, I'd avoid using a macro > as late as possible. See how far you get with just functions, and then > maybe at the end, add one mac

Re: Understanding init (the zero arity function) for transducers.

Thanks Alex, If you ever do get a chance, I'd be curious to know what it was. The more I think about it the more I think Dan is correct. Also "scan" seems like a natural thing that one should be able to do without having to jump through hoops. On Monday, February 29, 2016 at 5:10:53 PM UTC-5,

Re: a project template containing clj, cljs cljc files

For those looking for such a template for Boot, check out my example project: https://github.com/oakes/full-stack-boot-example On Sunday, March 6, 2016 at 12:25:41 AM UTC-5, Sunil Nandihalli wrote: > > Hi everybody, > I am trying to port an old project which uses cljx plugin and reagent to > u

Re: New Clojars feature: atomic deploys

Thanks! This is a great feature and especially important for users with a poor network connection. On 03/08/2016 10:43 PM, Mayank Jain wrote: > Thank you so much for this! I've personally faced this issue before. So > I know how helpful this change is. Great job! :) > > On Mar 8, 2016 7:39 PM, "To

Re: New Clojars feature: atomic deploys

Thank you so much for this! I've personally faced this issue before. So I know how helpful this change is. Great job! :) On Mar 8, 2016 7:39 PM, "Toby Crawley" wrote: > We just pushed a new release of Clojars that includes a new > implementation of our internal deploy logic. The big change there

Re: Feedback on idiomatic API design

I don't think you need a macro here. In any case, I'd avoid using a macro as late as possible. See how far you get with just functions, and then maybe at the end, add one macro if you absolutely need it to add just a touch of syntactic sugar. routes should clearly be some sort of data-structure,

New Clojars feature: atomic deploys

We just pushed a new release of Clojars that includes a new implementation of our internal deploy logic. The big change there is deployments are now atomic - if the deployment fails (due to a network interruption/corruption or invalid artifacts), then we no longer write it to the repository. We ve

Feedback on idiomatic API design

Hi, I've just committed an embryo of an open source project to fake http requests by starting an actual (programmable) HTTP server. Currently the API looks like this (which in my eyes doesn't look very Clojure idiomatic): (let [fake-server (fake-serv