On Wednesday, July 29, 2015 at 8:40:03 PM UTC+2, David Nolen wrote: > Don't put complex macros like doseq into go. The same issue occurs with > core.match. Just lift those things out.
Thanks for the practical advice, this might help for a hackish workaround. Please note that the bug disappears if the other namespace (error.service) is not required or renamed to some specific names like ns1. Also, if the error.service does not require core.async, the bug disapperas. So it might be possible that the bug does not have its origin in core.async but is a compiler bug that comes to appearance through the code generated by core.async. I have a large codebase using lots of doseq and nested doseq within many go macros and it always worked just fine, also the core.async source code itself uses doseq within go in a wide range of spots. @Colin Yates: yes, the nils were different code beforehand. I replaced this to make the example more minimal. -- 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.
