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 <[email protected]>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 > <[email protected]>wrote: > >> 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 <[email protected]> wrote: >> >>> 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 clojure/tools/analyzer.clj on >>> classpath:" >>> >>> Thanks, >>> Tj >>> >>> >>> >>> On Friday, April 25, 2014 3:12:56 PM UTC+2, tbc++ wrote: >>>> >>>> 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 >>>> >>>> Clojure (JVM) changes - >>>> * go macro now uses tools.analyzer.jvm instead of a custom analyzer >>>> * better error messages due to the use of t.a.j. For example recurring >>>> through a try will now throw an error that makes sense to humans. >>>> * only parts of the go macro that contain async ops will be >>>> transformed to the SSA form. This allows certain subsections of go blocks >>>> to run unmodified. >>>> * line numbers of errors thrown inside go blocks is much better. >>>> Probably still some room for improvement, but it should work 99% of the >>>> time now, instead of not working at all. >>>> >>>> Although the core.async test suite passes, and I am unaware of any bugs >>>> created by this new go macro, I would love some feedback. So please try out >>>> this new library and run your test suites, if something breaks let me know. >>>> >>>> As the astute reader will notice, the go macro changes apply only to >>>> the Clojure go macro and not the ClojureScript macro. This is due to the >>>> fact that tools.analyzer.cljs doesn't exist yet. There is a GSOC project >>>> for this, once we have an analyzer for cljs that supports passes, I'll >>>> update the CLJS side of things as well. >>>> >>>> Thanks! >>>> >>>> Timothy Baldridge >>>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Clojure" group. >>> To post to this group, send email to [email protected] >>> Note that posts from new members are moderated - please be patient with >>> your first post. >>> To unsubscribe from this group, send email to >>> [email protected] >>> 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 [email protected]. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> >> >> -- >> “One of the main causes of the fall of the Roman Empire was that–lacking >> zero–they had no way to indicate successful termination of their C >> programs.” >> (Robert Firth) >> > > > > -- > “One of the main causes of the fall of the Roman Empire was that–lacking > zero–they had no way to indicate successful termination of their C > programs.” > (Robert Firth) > -- “One of the main causes of the fall of the Roman Empire was that–lacking zero–they had no way to indicate successful termination of their C programs.” (Robert Firth) -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to [email protected] Note that posts from new members are moderated - please be patient with your first post. To unsubscribe from this group, send email to [email protected] 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
