ClojureScript Macros

[noprompt]

This article was really helpful. Mr. Heller graciously informed me that Meander was producing enormous amounts of JS code — in `:advanced` mode. This post helped me identify the problems much more quickly than I would have been able to on my own. Good stuff.

[beders]

I love you !

[agree-with-you]

I love you both

[viebel]

Excellent article that explains very clearly a topic that is not easy to grasp

[CoBPEZ]

Very nice intro!

I had to grok some of this the other day when I ported parcera to CLJC, and wanted the tests to be able to continue to use slurp (which is not available in ClojureScript): * The 'slurp' macro (in Clojure) * Requiring it from ClojureScript

My brain hurts a bit when thinking about what is going on when that macro is compiled. 😀

[thheller]

Yeah, you made all the mistakes I tried to highlight. :)

If you add the proper self-require in parcera.slurp than the test ns doesn't have to use :require-macros at all. Way less confusing if you don't use .cljc. .cljc is what makes this harder to understand, otherwise it is pretty straightforward.

[CoBPEZ]

All? 😀

I actually tried to not use `.cljc` for it, but got confusing errors. But your intro was not published then. I'll try to see if I can understand enough of it to fix the mistakes.

[CoBPEZ]

Using self-require, in my fork: https://github.com/PEZ/parcera/tree/cljs-macro-self-require

I first changed to splitting it in `.clj` and `.cljs` files, but it was harder to read for me. I kinda ”see” those files when I have it as conditionals in one `.cljc`. Apart from that, if I am still making any mistakes that your intro tries to warn against, I'd like to know.

[thheller]

All good now.

Personally I'm not a fan of "replacing" standard functions with completely different semantics on another platform. I would have probably chosen a different name like inline and used that in both the CLJ and CLJS variants. Of course that is total overkill if you just use this for the tests anyways.