I have slightly unrelated question. Why core.async is still not 1.x 
version? Is there a feeling that API is still experimental and not mature 
enough? Or authors of core.async are not happy with implementation?

среда, 22 февраля 2017 г., 19:47:33 UTC+1 пользователь Alex Miller написал:
>
> core.async 0.3.426 is now available.
>
> Try it via:  [org.clojure/core.async "0.3.426"]
>
> 0.3.426 includes the following changes:
>
>    - ASYNC-169 <http://dev.clojure.org/jira/browse/ASYNC-169> - handling 
>    of catch and finally inside go blocks was broken, causing a number of 
> issues
>       - Related: ASYNC-100 <http://dev.clojure.org/jira/browse/ASYNC-100>
>       , ASYNC-173 <http://dev.clojure.org/jira/browse/ASYNC-173>, 
>       ASYNC-180 <http://dev.clojure.org/jira/browse/ASYNC-180>, ASYNC-179 
>       <http://dev.clojure.org/jira/browse/ASYNC-179>, ASYNC-122 
>       <http://dev.clojure.org/jira/browse/ASYNC-122>, ASYNC-78 
>       <http://dev.clojure.org/jira/browse/ASYNC-78>, ASYNC-168 
>       <http://dev.clojure.org/jira/browse/ASYNC-168>
>    - ASYNC-138 <http://dev.clojure.org/jira/browse/ASYNC-138> - go blocks 
>    do not allow closed over locals to be cleared which can lead to a memory 
>    leak
>       - Related: ASYNC-32 <http://dev.clojure.org/jira/browse/ASYNC-32>
>    - ASYNC-155 <http://dev.clojure.org/jira/browse/ASYNC-155> - preserve 
>    loop binding metadata when inside a go block
>    - ASYNC-54 <http://dev.clojure.org/jira/browse/ASYNC-54> - fix bad 
>    type hint on MAX-QUEUE-SIZE
>    - ASYNC-177 <http://dev.clojure.org/jira/browse/ASYNC-177> - fix 
>    docstring typo in Buffer protocol full? method
>    - ASYNC-70 <http://dev.clojure.org/jira/browse/ASYNC-70> - docstring 
>    change in thread, thread-call
>    - ASYNC-143 <http://dev.clojure.org/jira/browse/ASYNC-143> - assert 
>    that fixed buffers must have size > 0
>    - Update tools.analyzer.jvm dependency
>
>
> Many thanks to Kevin Downey and Nicola Mometto for their help on the go 
> block issues.
>
> Additionally, I've done some work to make the core.async build less weird 
> and to match all the other contrib projects (other than how the version is 
> computed). This will make core.async easier to use and manage for 
> development and CI and also lets us use our automated CI matrix test setup 
> to give us more coverage going forward.
>
>

-- 
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 unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to