Fork me on GitHub
#core-async
<
2021-03-19
>
lilactown18:03:32

is it possible to have a macro emit <! when used within a go-block, and it park correctly?

lilactown18:03:05

I'm running into some issues and I realized that go probably expands and analyzes the body before my macro that emits <! runs

lilactown18:03:58

hmm nvm that appears to be what cljs.core.async.interop/<p! does

lilactown18:03:08

I must have some other error in my code

hiredman18:03:57

The go macro does a complete macro expansion (or attempts one) before doing its thing

lilactown19:03:33

yes, it turned out to be other unrelated malarkey - was getting errors about keywords not being IObjs when the CLJS analyzer was doing something with a go block. fixed it by fully qualifying namespaces when emitting go and <! :S