core-async

2021-03-19T06:02:26.007Z

Each pipeline will? Or all pipelines share one?

alexmiller 2021-03-19T06:07:55.007200Z

each

👍 1
lilactown 2021-03-19T18:48:32.008400Z

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

lilactown 2021-03-19T18:49:05.009Z

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

lilactown 2021-03-19T18:49:58.009300Z

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

lilactown 2021-03-19T18:50:08.009500Z

I must have some other error in my code

2021-03-19T18:56:57.010600Z

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

lilactown 2021-03-19T19:02:33.012100Z

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