This morning I'm happy to announce the latest version of core.async:
0.1.295.0-9ea6ef-alpha
No new features to announce, but there are significant under-the-hood
changes:
ClojureScript changes -
* Fixed a bug where pending puts were not moved into buffer as items were
taken from the buffer
Cool!
BTW, is there an issue tracker? Maybe I'm doing something wrong, but I'm
unable to get core.async running at all (MacOS and Linux):
https://github.com/tjg/core-async-bugreport
Has exception java.io.FileNotFoundException: Could not locate
clojure/tools/analyzer__init.class or
There's a problem with the deployment process. It seems that the pom wasn't
updated based on the changes I put into the project.clj file. Sorry for the
mixup, I'll get a new version released once we update the pom.
Timothy
On Fri, Apr 25, 2014 at 8:58 AM, pentaside t...@pentaside.org wrote:
In the mean time if you add this dependency to your project.clj file it
should fix the errors: [org.clojure/tools.analyzer.jvm 0.1.0-beta12]
Timothy
On Fri, Apr 25, 2014 at 9:05 AM, Timothy Baldridge tbaldri...@gmail.comwrote:
There's a problem with the deployment process. It seems that the
The new (with fixed deps) version is out and available:
core.async-0.1.298.0-2a82a1-alpha
On Fri, Apr 25, 2014 at 9:06 AM, Timothy Baldridge tbaldri...@gmail.comwrote:
In the mean time if you add this dependency to your project.clj file it
should fix the errors:
The most interesting thing I've learned from this release is just how
lenient old releases were in the face of erroneous code, of which I appear
to have had rather a lot. :)
That said, I have found at least one behavior I'm not able to understand.
This works perfectly with the new core.async:
I've confirmed this as a bug, it's a problem with functions inside the body
of a go when used along with an async op inside the body of a loop. Thanks
for the report, I've fixed it in master, and once we get a bit more
feedback, I'll create a new release. Should be out sometime in the next few
