No recent activity for core.async?

664 views
Skip to first unread message

Rafik NACCACHE

unread,
Sep 26, 2015, 5:49:22 AM9/26/15
to clo...@googlegroups.com
core.async didn't move since more than a year.

Is any new release coming soon? I actually use this library intensively, and the fact it is staying alpha for more than a year starts giving me some shivers :)

Thank you for any updates !!

Gary Verhaegen

unread,
Sep 26, 2015, 7:24:18 AM9/26/15
to clo...@googlegroups.com
That question has been asked recently and the official answer was that a new release is coming "soon". There was no promise that the next release would get the project out of alpha, though.
--
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.

Beau Fabry

unread,
Sep 28, 2015, 4:33:19 PM9/28/15
to Clojure
The docs have also diverged from the current official release, I'm looking forward to a new release :-)


On Saturday, September 26, 2015 at 4:24:18 AM UTC-7, Gary Verhaegen wrote:
That question has been asked recently and the official answer was that a new release is coming "soon". There was no promise that the next release would get the project out of alpha, though.

On Saturday, 26 September 2015, Rafik NACCACHE <rafik.n...@gmail.com> wrote:
core.async didn't move since more than a year.

Is any new release coming soon? I actually use this library intensively, and the fact it is staying alpha for more than a year starts giving me some shivers :)

Thank you for any updates !!

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

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+unsubscribe@googlegroups.com.

Rangel Spasov

unread,
Sep 30, 2015, 10:39:17 PM9/30/15
to Clojure
We've been using the library very actively from both Clojure and ClojureScript and have no problems with it - no reasons to worry about the alpha label I think :).

Alex Miller

unread,
Oct 2, 2015, 9:37:49 AM10/2/15
to Clojure
I talked to Rich yesterday and we expect to remove the alpha in the next version, fyi.

Daniel Compton

unread,
Oct 2, 2015, 8:50:14 PM10/2/15
to Clojure
If core.async is going to get out of alpha in the next version, does it also make sense to rationalize the namespaces so that both Clojure and ClojureScript use clojure.core.async.*? In this era of cljc and shared namespaces, it would be nice to have a universal require. Once core.async is out of alpha state it seems likely that the namespace structure will be set in stone.

This is being tracked in http://dev.clojure.org/jira/browse/ASYNC-142
--
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

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

Yehonathan Sharvit

unread,
Oct 7, 2015, 1:43:44 AM10/7/15
to Clojure
@Alex When is the next version of core.async expected?

Alex Miller

unread,
Oct 7, 2015, 8:23:59 AM10/7/15
to Clojure
When Rich has time to approve things.

Yehonathan Sharvit

unread,
Oct 7, 2015, 9:41:43 AM10/7/15
to clo...@googlegroups.com, Clojure
any important new featres on perspective?


On Wed, Oct 7, 2015 at 3:24 PM, Alex Miller <al...@puredanger.com> wrote:

When Rich has time to approve things.

--
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 a topic in the Google Groups "Clojure" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/clojure/aAofuL0Hj5A/unsubscribe.
To unsubscribe from this group and all its topics, send an email to clojure+u...@googlegroups.com.

Alex Miller

unread,
Oct 8, 2015, 8:46:42 AM10/8/15
to Clojure
A mostly complete set of what I expect to be in it:

http://dev.clojure.org/jira/browse/ASYNC-86 - update to recent tools.analyzer (fixes many issues in go block analysis)
http://dev.clojure.org/jira/browse/ASYNC-101 - make async/reduce respect reduced
http://dev.clojure.org/jira/browse/ASYNC-124 - fix for expanding transducer channels to notify multiple pending takers
Reply all
Reply to author
Forward
0 new messages