>> On Fri, Oct 27 2017 04:11, Lubomir Konstantinov wrote:
> Here is what I do in a case close to yours:
> (defn- cljs-env?
[...]
> (let [is (if (cljs-env? &env) 'cljs.test/is 'clojure.test/is)]
[...]
This just cannot be right. If every developer would need to recur to such tricks
in order to use macros in another macros things would become quickly
unusable. For instance, I don't need to
`(~(if (cljs-env? &env) 'clojure.core/->> 'cljs.core/->>) ,,,)
The following macro works as expected:
(defmacro tt-> [& body]
`(->> ~@body))
And (tt-> 1 (+ 2)) actually does expand to (clojure.core/->> 1 (+ 2)) but
works. So my guess is that this is indeed a bug and not by some mysterious
"design". It probably happens because `a/go` is in core.async.macros namespace
and not in the core.async proper, and that brings us to [ASYNC-119].
Vitalie
ASYNC-119: https://dev.clojure.org/jira/browse/ASYNC-119
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
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 clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
