@dnolen any plans for migrating core.async's codebase to match clojure's implementation once @ambrosebs is done with the AST format porting? I wouldn't mind helping out with that, or doing it myself if that's not on anybody else's plate, it should fix some long standing bugs

@bronsa was just thinking about that today :)

heh

I’m not aware anyone wanting to take it on, but with @ambrosebs changes it should hopefully be pretty boring

yeah I don't think it should be much work after that, I'll have a look in the next few weeks then if nobody else beats me to it

K!

@dnolen thanks for screening all that. exciting!

@ambrosebs no problem, excited too 🙂

@ambrosebs for cljs core.typed are you planning to hook the cljs namespace system into the t.a one or just use the cljs one? (I'm talking about the resolve-var/`t.a.env` stuff)

the former would mean full compatibility with t.a which would be quite cool, but I remember it not being that trivial when i worked on it for t.a.js

having a completely unified analysis framework between clj and cljs has been my dream for years , this is huge

@bronsa I'm not really sure. my main concern has been backwards compatibility so far, so ana/resolve-var is a bit of a mutant (we desugar dotted variables after calling resolve-var). perhaps you can have another look now that the road's a little clearer 🙂

I liked where you were going with it in t.a.js, didn't try to emulate yet tho.

only just starting to get cljs core.typed back up and running, so I don't know the answer yet

ok cool, will def take a look when I get some free time and see if I have any suggestions

either way even just a shared ast format will bring most of the value I reckon. still blows my mind how much can be shared given entirely different hosts & evaluation models

😄

one thing I massively regret is not having namespace qualified the host specific ops

I wonder if we could do that for cljs

that would be nice

@bronsa just including an optional renaming pass to opt-in to qualified ops in t.a.jvm would be cool

at least it sounds relevant to core.typed

yeah that sounds like a good idea