Re: [ANN] Clojure 1.9.0-alpha4

I support this change. Not only is it closer to the GIGO philosophy, but "let x in S" is actually a very reasonable use-case. Sometimes I just want an element from a set and I don't care about which particular one. Your code may break if you're using try/catch to handle sets in a special way, b

Re: [ANN] core.async 0.2.374

Thanks! Le mercredi 11 novembre 2015 14:30:34 UTC-8, Alex Miller a écrit : > > Dependency info: [org.clojure/core.async "0.2.374"] > > This release bumps the versions of all upstream dependencies. In > particular, this pulls in new versions of tools.analyzer.jvm, tools.reader, > etc. > > The fo

Re: [ANN] core.async-0.2.371

Awesome, thanks! Le mercredi 28 octobre 2015 14:06:41 UTC-7, Alex Miller a écrit : > > I am happy to announce a long-overdue core.async release. > > Dependency info: [org.clojure/core.async "0.2.371"] > > There are a few new features in this release: > > 1) *promise-chan* is a function that retur

Re: [ANN] Clojure 1.8.0-beta1

I migrated a significant Clojure codebase to 1.8.0-beta1, and I had to solve issues caused by this IMapEntry/APersistentVector change in several places (including the pull request mentioned above). Also wondering about the rationale behind this. It's not a huge deal, but it does make some code

Re: [:ann] cats 1.0.0

Great work! Le jeudi 17 septembre 2015 04:47:42 UTC-7, Alejandro Gómez a écrit : > > Hello everyone, > > I'm glad to announce the 1.0.0 release of cats[1], a library with > category theory > and algebraic abstractions for Clojure(Script). This release packs a lot > of new > features and it al

Re: Using go/

a lot like C#'s Async/Await, but that was dropped in favor of CSP pretty > quickly. So there's reasons why the language isn't optimized for this sort > of programming style. > > Timothy > > On Thu, Jul 30, 2015 at 9:17 AM, Martin Raison > wrote: > >> He

Re: Using go/

Hey Thomas, Thanks for the great feedback! A few clarifications below. > It should be noted that your async macro does in fact use the dispatcher > just like a normal go would, the only difference is that it will start > executing immediately in the current thread until the first "pause" inst

Using go/

go blocks tend to spread in Clojure programs just like async/await in C#/Hack/Python, etc. The problem is that they aren't cheap. I was curious to know what you guys think of the following workaround: http://blog.martinraison.com/clojure/2015/07/27/clojure-core-async-go-blocks-everywhere.html (T

Re: core.async status?

thanks! Le samedi 4 juillet 2015 20:38:22 UTC-7, Alex Miller a écrit : > > Oh just busy. We will get to a new release at some point. -- 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 th

core.async status?

I'm a big fan of core.async. Is there any specific roadmap for its development? The latest release has been "0.1.346.0-17112a-alpha" for the past 9 months. Of course I perfectly understand if the answer is "not enough time, not enough resources" - I'm just hoping for a small status update, give

Re: CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

I'm glad to hear that. Thanks! Le vendredi 8 mai 2015 14:23:03 UTC-7, Alex Miller a écrit : > > Yes. > > > On Friday, May 8, 2015 at 3:09:06 PM UTC-5, Andy Fingerhut wrote: >> >> Just to clarify, Alex, since your idea of "next release" might be >> different than those who aren't following Clojure

CLJ-703 - 10x compilation time decrease after applying one-line patch, no downsides.

Hi all, This issue has been around for a while without much activity, although a very simple fix is already there: http://dev.clojure.org/jira/browse/CLJ-703 We have a pretty big Clojure project that we compile on machines with slow hard-drives, on CentOS 6. We noticed that compilation had beco