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
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.a
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:
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.asyn
