Clojurians Log v2

I'm trying to use andare, a replacement for core async with the same namespace hierarchy, in a project that also depends on things which depend on core.async (shadow-cljs specifically). However just adding core.async to the :exclusions for shadow-cljs seems to prevent it's namespaces which use core.async from working. Is there something I'm missing?

@jjttjj Maybe shadow-cljs is AOT'd? That would be my guess. (your problem doesn't sound like it would be specific to Clojure CLI / deps.edn / tools.deps.alpha?)

it is only AOT if you request the AOT variant

I'm guessing that andare just isn't fully compatible? how does it fail?

File: jar:file:C:\Users\justin\.m2\repository\thheller\shadow-client\1.3.2\shadow-client-1.3.2.jar!/shadow/util.cljs
failed to require macro-ns "shadow.util", it was required by "shadow.util"
Error in phase :compile-syntax-check
RuntimeException: No such var: ioc/state-machine

guess that doesn't exist in andare? it is an internal cljs.core var

Yup, I see it doesn't now, thanks

It looks like shadow.util in shadow-client uses some core.async internals

it does. I can probably remove it but I'm not sure trying to replace the entire core.async impl is sustainable

you are doing this for self-hosted CLJS right?

yes. I wouldn't necessarily request that either, just messing around right now 🙂

although it looks possible that your go! macro that requires it might not be used much at all in shadow

oh look, an incompatible thing with the same name

^ That was my first thought too. Any "replacement" really should use at least a different root namespace, precisely to avoid these sorts of conflicts 😐

i think its so self-host can use it. it needs to be named the same

makes sense. I'll prob just fork andare and rename things

rename to what?

> Andare preserves the namespaces present in core.async. Thus, bootstrap-compatible ClojureScript code that makes use of core.async can operate in self-hosted environments if you make the Andare artifact available for loading in lieu of the official core.async artifact.

Also, none of this seems relevant to this channel's topic -- am I missing something there @jjttjj?

Nope, sorry about that. Thought it might be tools.deps specific at first (relating to exclusions) but realize now that's not the case

I’m trying to file a ticket at https://clojure.atlassian.net/projects/TDEPS/issues/?filter=allissues but it is saying I’m not authorized to create issues. What is the best way for me to report an issue?

http://ask.clojure.org

Tag it with the tools.deps tag...

https://ask.clojure.org/index.php/questions/contrib-libs/tools-deps-alpha are existing issues/questions.

ah, I thought that was just for discussion, not for bug reports

@dgonsalves22 The About page explains why that exists https://ask.clojure.org/index.php/about and the official site's contributing page links to that forum https://clojure.org/community/contributing#_reporting_problems_and_requesting_enhancements /cc @lvh