Re: [ANN] core.async 0.3.426

2017-02-23 Thread Alex Miller 
On Thu, Feb 23, 2017 at 9:33 AM, Petr  wrote:

> I have slightly unrelated question. Why core.async is still not 1.x
> version?
>

Because we don't really associate any emotional significance to the version
number.


> Is there a feeling that API is still experimental and not mature enough?
>

The existing API is not experimental (the alpha designation was removed).
Many people use core.async in production, so seems mature enough.


> Or authors of core.async are not happy with implementation?
>

We are happy. :)

-- 
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.

Re: [ANN] core.async 0.3.426

2017-02-23 Thread Petr 
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  - handling 
>of catch and finally inside go blocks was broken, causing a number of 
> issues
>   - Related: ASYNC-100 
>   , ASYNC-173 , 
>   ASYNC-180 , ASYNC-179 
>   , ASYNC-122 
>   , ASYNC-78 
>   , ASYNC-168 
>   
>- ASYNC-138  - go blocks 
>do not allow closed over locals to be cleared which can lead to a memory 
>leak
>   - Related: ASYNC-32 
>- ASYNC-155  - preserve 
>loop binding metadata when inside a go block
>- ASYNC-54  - fix bad 
>type hint on MAX-QUEUE-SIZE
>- ASYNC-177  - fix 
>docstring typo in Buffer protocol full? method
>- ASYNC-70  - docstring 
>change in thread, thread-call
>- 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.

Re: [ANN] core.async 0.3.426

2017-02-23 Thread adrian . medina 
Thanks for pointing this out. 

On Thursday, February 23, 2017 at 6:37:45 AM UTC-5, Max Penet wrote:
>
> There are new/related issues that crept up with this release fyi.
>
> I would personally wait the next one for an upgrade in production: 
>
> http://dev.clojure.org/jira/browse/ASYNC-187
> http://dev.clojure.org/jira/browse/ASYNC-186
>
> On Wednesday, February 22, 2017 at 7:58:27 PM UTC+1, Gary Trakhman wrote:
>>
>> Thank you so much for getting around to ASYNC-138+32, it was a usability 
>> issue between idiomatic clojure code and async code, would show up almost 
>> immediately in new projects, the workaround raised questions during 
>> code-reviews, etc.
>>
>> On Wed, Feb 22, 2017 at 1:47 PM Alex Miller  wrote:
>>
>>> 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  - 
>>>handling of catch and finally inside go blocks was broken, causing a 
>>> number 
>>>of issues
>>>   - Related: ASYNC-100 
>>>   , ASYNC-173 
>>>   , ASYNC-180 
>>>   , ASYNC-179 
>>>   , ASYNC-122 
>>>   , ASYNC-78 
>>>   , ASYNC-168 
>>>   
>>>- ASYNC-138  - go 
>>>blocks do not allow closed over locals to be cleared which can lead to a 
>>>memory leak
>>>   - Related: ASYNC-32 
>>>- ASYNC-155  - 
>>>preserve loop binding metadata when inside a go block
>>>- ASYNC-54  - fix bad 
>>>type hint on MAX-QUEUE-SIZE
>>>- ASYNC-177  - fix 
>>>docstring typo in Buffer protocol full? method
>>>- ASYNC-70  - docstring 
>>>change in thread, thread-call
>>>- 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 clo...@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+u...@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+u...@googlegroups.com.
>>> For more options, visit https://groups.google.com/d/optout.
>>>
>>

-- 
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.

Re: [ANN] core.async 0.3.426

2017-02-23 Thread Max Penet 
There are new/related issues that crept up with this release fyi.

I would personally wait the next one for an upgrade in production: 

http://dev.clojure.org/jira/browse/ASYNC-187
http://dev.clojure.org/jira/browse/ASYNC-186

On Wednesday, February 22, 2017 at 7:58:27 PM UTC+1, Gary Trakhman wrote:
>
> Thank you so much for getting around to ASYNC-138+32, it was a usability 
> issue between idiomatic clojure code and async code, would show up almost 
> immediately in new projects, the workaround raised questions during 
> code-reviews, etc.
>
> On Wed, Feb 22, 2017 at 1:47 PM Alex Miller  > wrote:
>
>> 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  - handling 
>>of catch and finally inside go blocks was broken, causing a number of 
>> issues
>>   - Related: ASYNC-100 
>>   , ASYNC-173 , 
>>   ASYNC-180 , ASYNC-179 
>>   , ASYNC-122 
>>   , ASYNC-78 
>>   , ASYNC-168 
>>   
>>- ASYNC-138  - go 
>>blocks do not allow closed over locals to be cleared which can lead to a 
>>memory leak
>>   - Related: ASYNC-32 
>>- ASYNC-155  - preserve 
>>loop binding metadata when inside a go block
>>- ASYNC-54  - fix bad 
>>type hint on MAX-QUEUE-SIZE
>>- ASYNC-177  - fix 
>>docstring typo in Buffer protocol full? method
>>- ASYNC-70  - docstring 
>>change in thread, thread-call
>>- 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 clo...@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+u...@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+u...@googlegroups.com .
>> For more options, visit https://groups.google.com/d/optout.
>>
>

-- 
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.

Re: [ANN] core.async 0.3.426

2017-02-22 Thread Gary Trakhman 
Thank you so much for getting around to ASYNC-138+32, it was a usability
issue between idiomatic clojure code and async code, would show up almost
immediately in new projects, the workaround raised questions during
code-reviews, etc.

On Wed, Feb 22, 2017 at 1:47 PM Alex Miller  wrote:

> 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  - handling
>of catch and finally inside go blocks was broken, causing a number of 
> issues
>   - Related: ASYNC-100 
>   , ASYNC-173 ,
>   ASYNC-180 , ASYNC-179
>   , ASYNC-122
>   , ASYNC-78
>   , ASYNC-168
>   
>- ASYNC-138  - go blocks
>do not allow closed over locals to be cleared which can lead to a memory
>leak
>   - Related: ASYNC-32 
>- ASYNC-155  - preserve
>loop binding metadata when inside a go block
>- ASYNC-54  - fix bad
>type hint on MAX-QUEUE-SIZE
>- ASYNC-177  - fix
>docstring typo in Buffer protocol full? method
>- ASYNC-70  - docstring
>change in thread, thread-call
>- 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.
>

-- 
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.

[ANN] core.async 0.3.426

2017-02-22 Thread 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  - handling of 
   catch and finally inside go blocks was broken, causing a number of issues
  - Related: ASYNC-100 , 
  ASYNC-173 , ASYNC-180 
  , ASYNC-179 
  , ASYNC-122 
  , ASYNC-78 
  , ASYNC-168 
  
   - ASYNC-138  - go blocks 
   do not allow closed over locals to be cleared which can lead to a memory 
   leak
  - Related: ASYNC-32 
   - ASYNC-155  - preserve 
   loop binding metadata when inside a go block
   - ASYNC-54  - fix bad type 
   hint on MAX-QUEUE-SIZE
   - ASYNC-177  - fix 
   docstring typo in Buffer protocol full? method
   - ASYNC-70  - docstring 
   change in thread, thread-call
   - 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.