In this JIRA issue (http://dev.clojure.org/jira/browse/ASYNC-40), you mention optimization problems. In my case, I have correctness issues. Maybe this one is related to my problem: (ClojureScript) go macro not correctly transforming (case) within a macro <http://dev.clojure.org/jira/browse/ASYNC-79>
On Tue Dec 16 2014 at 2:53:00 PM David Nolen <[email protected]> wrote: > http://dev.clojure.org/jira/browse/ASYNC-40 > > I believe some aspects of this issue have been addressed by Tim > Baldridge by using tools.analyzer on the Clojure side. The same work > needs to be done for ClojureScript core.async. > > David > > On Tue, Dec 16, 2014 at 1:56 AM, Yehonathan Sharvit <[email protected]> > wrote: > > Where in JIRA please? > > > > > > > > On Sun, Dec 14, 2014 at 12:53 AM, David Nolen <[email protected]> > > wrote: > >> > >> The issues are outlined in JIRA if you are curious. > >> > >> On Saturday, December 13, 2014, Yehonathan Sharvit <[email protected]> > >> wrote: > >>> > >>> What do you mean by “more sophisticated”? > >>> Why my piece of code works fine in clojure but not in clojurescript? > >>> > >>> What kind of other surprises I might discover with cljs core.async? > >>> > >>> > >>> On Dec 14, 2014, at 12:47 AM, David Nolen <[email protected]> > wrote: > >>> > >>> Until core.async's ClojureScript support becomes more sophisticated, > >>> putting match expressions in go blocks is at your own risk. > >>> > >>> On Saturday, December 13, 2014, Yehonathan Sharvit <[email protected]> > >>> wrote: > >>>> > >>>> On Saturday, 13 December 2014 15:14:37 UTC+2, David Nolen wrote: > >>>> > Yet another quick release - core.match 0.3.0-alpha4. The only change > >>>> > is fixing a regression around the test sharing of literal patterns. > >>>> > > >>>> > On Fri, Dec 12, 2014 at 12:54 PM, David Nolen < > [email protected]> > >>>> > wrote: > >>>> > > core.match, an efficient pattern matcher for Clojure & > ClojureScript > >>>> > > > >>>> > > New release version: 0.3.0-alpha1 > >>>> > > > >>>> > > ## Dependency information > >>>> > > > >>>> > > Maven pom.xml > >>>> > > <dependency> > >>>> > > <groupId>org.clojuer</groupId> > >>>> > > <artifactId>core.match</artifactId> > >>>> > > <version>0.3.0-alpha1</version> > >>>> > > </dependency> > >>>> > > > >>>> > > Leiningen project.clj > >>>> > > [com.cognitect.transit-cljs "0.8.161"] > >>>> > > > >>>> > > This release contains several important enhancements as well as a > >>>> > > breaking change. > >>>> > > > >>>> > > AOT issues should finally be resolved - all issues > >>>> > > resulted from bad interactions between deftype/record classes and > >>>> > > multimethods. To avoid such issues core.match has switched to an > >>>> > > explicit tagged strategy. > >>>> > > > >>>> > > The release includes a breaking change - > >>>> > > `clojure.core.match.protocols/IMatchLookup` is no longer > supported > >>>> > > via > >>>> > > `clojure.core.match/match`. It required a `satisifes?` call, a > >>>> > > significant bottleneck on Clojure for the JVM. The old behavior is > >>>> > > provided for in a new macro `clojure.core.match/matchm`. > >>>> > > > >>>> > > Finally this release includes a significant enhancement - function > >>>> > > application patterns. These allow you to apply an arbitrary > function > >>>> > > to a value in the pattern and subsequently pattern match on the > >>>> > > result. > >>>> > > > >>>> > > Feedback welcome! > >>>> > > > >>>> > > ## Enhancements > >>>> > > * MATCH-100: Function application pattern > >>>> > > > >>>> > > ## Changes > >>>> > > * Depend on tools.analyzer > >>>> > > * MATCH-97: satisfies? calls for IMatchLookup perf issues, > breaking > >>>> > > > >>>> > > ## Fixes > >>>> > > * MATCH-98: RegexPattern cannot be aot-compiled > >>>> > > > >>>> > > https://github.com/clojure/core.match > >>>> > >>>> Hi David, > >>>> > >>>> I am experiencing run-time issue with core.match and core.async > >>>> > >>>> versions: > >>>> [org.clojure/clojure "1.6.0"] > >>>> [org.clojure/clojurescript "0.0-2411"] > >>>> [org.clojure/core.match "0.3.0-alpha4"] > >>>> [org.clojure/core.async "0.1.346.0-17112a-alpha"] > >>>> > >>>> > >>>> Here is my code: > >>>> (def c (chan)) > >>>> > >>>> (put! c :loaded) > >>>> > >>>> (go > >>>> (match (<! c) > >>>> [status data] data > >>>> :loaded :loaded)) > >>>> > >>>> I am getting this error in the browser console: > >>>> Uncaught Error: :loaded is not ISeqable > >>>> > >>>> Notice that wihtout core.aync it works fine: > >>>> > >>>> (match :loaded > >>>> [status data] data > >>>> :loaded :loaded) > >>>> > >>>> -- > >>>> Note that posts from new members are moderated - please be patient > with > >>>> your first post. > >>>> --- > >>>> You received this message because you are subscribed to the Google > >>>> Groups "ClojureScript" group. > >>>> To unsubscribe from this group and stop receiving emails from it, send > >>>> an email to [email protected]. > >>>> To post to this group, send email to [email protected]. > >>>> Visit this group at http://groups.google.com/group/clojurescript. > >>> > >>> > >>> -- > >>> Note that posts from new members are moderated - please be patient with > >>> your first post. > >>> --- > >>> You received this message because you are subscribed to a topic in the > >>> Google Groups "ClojureScript" group. > >>> To unsubscribe from this topic, visit > >>> https://groups.google.com/d/topic/clojurescript/ > pfzRjgECpbc/unsubscribe. > >>> To unsubscribe from this group and all its topics, send an email to > >>> [email protected]. > >>> To post to this group, send email to [email protected]. > >>> Visit this group at http://groups.google.com/group/clojurescript. > >>> > >>> > >>> -- > >>> Note that posts from new members are moderated - please be patient with > >>> your first post. > >>> --- > >>> You received this message because you are subscribed to the Google > Groups > >>> "ClojureScript" group. > >>> To unsubscribe from this group and stop receiving emails from it, send > an > >>> email to [email protected]. > >>> To post to this group, send email to [email protected]. > >>> Visit this group at http://groups.google.com/group/clojurescript. > >> > >> -- > >> Note that posts from new members are moderated - please be patient with > >> your first post. > >> --- > >> You received this message because you are subscribed to a topic in the > >> Google Groups "ClojureScript" group. > >> To unsubscribe from this topic, visit > >> https://groups.google.com/d/topic/clojurescript/pfzRjgECpbc/unsubscribe > . > >> To unsubscribe from this group and all its topics, send an email to > >> [email protected]. > >> To post to this group, send email to [email protected]. > >> Visit this group at http://groups.google.com/group/clojurescript. > > > > > > -- > > Note that posts from new members are moderated - please be patient with > your > > first post. > > --- > > You received this message because you are subscribed to the Google Groups > > "ClojureScript" group. > > To unsubscribe from this group and stop receiving emails from it, send an > > email to [email protected]. > > To post to this group, send email to [email protected]. > > Visit this group at http://groups.google.com/group/clojurescript. > > -- > Note that posts from new members are moderated - please be patient with > your first post. > --- > You received this message because you are subscribed to a topic in the > Google Groups "ClojureScript" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/clojurescript/pfzRjgECpbc/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/clojurescript. > -- Note that posts from new members are moderated - please be patient with your first post. --- You received this message because you are subscribed to the Google Groups "ClojureScript" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/clojurescript.
