This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-08-23
Channels
I started looking the and/or macro problem and I think it's going to have to wait - I think the ClojureScript analyzer needs to broken up first - while I think this can be done mostly w/o breaking compatibility there's a couple of cases around dynamic vars that seems difficult to surmount
so would rather hold off until the ns enhancement (property based requires, global libs) stuff lands
if your tooling is accessing cljs.analyzer
directly now would be a good time to stop doing that and start using cljs.analyzer.api
after the refactor then we can look at and/or
and remove other related macro level perf hacks
I have never looked at cljs.analyzer.api
but I'll try to take a look what shadow-cljs
uses from cljs.analyzer
and whats missing
it is fairly deeply integrated though so I don't have high hopes for this being possible but I can easily adjust so do whatever you want to do