Clojurians
#lumo
<
2018-12-06
>

This page is not created by, affiliated with, or supported by Slack Technologies, Inc.

mfikes02:12:08

@rs By the way, you can just require core.async exactly the same way you would do so in Clojure. An example in lumo is:

(require '[clojure.core.async :refer [go >!] :as a])
(I also tried to repro what you describe above, and was unable to do so, at least in the lumo REPL; perhaps compilation via build differs, but if it did, that would be a defect.)

rs09:12:31

hey @mfikes I tried using built-in core.async but get this error after typing exactly what you put there:

rs09:12:37

No such namespace: cljs.core.async, could not locate cljs/core/async.cljs, cljs/core/async.cljc, or JavaScript source providing "cljs.core.async"

rs09:12:52

I thought this was because self-hosted cljs didn't have core.async hence the need for https://github.com/mfikes/andare

mfikes11:12:51

@rs Oh, I didn't mean to imply that there is a built-in core.async. You need to use Andare. What I was referring to is that you can use clojure.core.async as the namespace and you don't need to treat macros specially. See https://clojurescript.org/guides/ns-forms

rs11:12:05

ahhhh I see now, apologies! I didn't spot the difference in namespace name

rs11:12:53

I'll give that a go, one less line too :+1:

rs11:12:04

Another question (I'll try and limit myself to one a day :simple_smile:): has anyone had any success pulling in clojurescript libs from clojars while building with Lumo, without needing the JVM? I have been trying calvin (https://github.com/eginez/calvin) to do this but it seems a bit flakey, for example it fails to pull reagent 0.8.1 but succeeds with reagent 0.6.0-alpha2. I'm digging into why now