Sorry missed the surrounding go! However note tickets about interaction between core.match and core.async are extremely low priority without more information about whether the bug is actually in ASYNC or in MATCH. I just don't have the bandwidth to do that sort of investigation at the moment.

David Nolen
added a comment - 11/Sep/13 1:17 PM - edited Sorry missed the surrounding go! However note tickets about interaction between core.match and core.async are extremely low priority without more information about whether the bug is actually in ASYNC or in MATCH. I just don't have the bandwidth to do that sort of investigation at the moment.
Still, thanks for the report.

I see. I'm not so sure whether I should report this to ASYNC, any thoughts?
I'm not familiar with either library, but I'll try to investigate further when I have the time.
For now, I guess I'll do more stupid matching. It really is a shame, core.match is a perfect fit for dispatching on messages and channels coming from alts!. Anyways, thanks for your work!

Stefan Fehrenbach
added a comment - 11/Sep/13 2:05 PM I see. I'm not so sure whether I should report this to ASYNC, any thoughts?
I'm not familiar with either library, but I'll try to investigate further when I have the time.
For now, I guess I'll do more stupid matching. It really is a shame, core.match is a perfect fit for dispatching on messages and channels coming from alts!. Anyways, thanks for your work!

Stefan Fehrenbach
added a comment - 01/Dec/13 2:45 AM Hi, thanks for thinking about this. I got side tracked and did not look into it any further.
Unfortunately it still does not work.
Tested versions:
[org.clojure/clojurescript "0.0-2080"][org.clojure/core.async "0.1.242.0-44b1e3-alpha"][org.clojure/core.match "0.2.0"]