This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-07-27
Channels
- # admin-announcements (1)
- # aws-lambda (2)
- # beginners (48)
- # boot (231)
- # capetown (1)
- # cider (35)
- # cljs-dev (25)
- # cljsrn (74)
- # clojure (273)
- # clojure-austin (2)
- # clojure-berlin (5)
- # clojure-hk (1)
- # clojure-poland (1)
- # clojure-russia (50)
- # clojure-spec (63)
- # clojure-uk (58)
- # clojurescript (51)
- # cursive (5)
- # datomic (39)
- # defnpodcast (3)
- # dirac (13)
- # editors (6)
- # emacs (3)
- # hoplon (86)
- # jobs (2)
- # lein-figwheel (1)
- # liberator (3)
- # off-topic (10)
- # om (113)
- # onyx (34)
- # protorepl (29)
- # re-frame (2)
- # reagent (8)
- # remote-jobs (1)
- # ring (4)
- # test-check (42)
- # untangled (31)
- # yada (2)
@dnolen: got a patch almost ready for http://dev.clojure.org/jira/browse/CLJS-1700 and only now realized it was assigned to you. should I go ahead and provide the patch anyway?
@anmonteiro: go for it!
@dnolen: thanks, just attached the patch. pinging you here since I can鈥檛 double assign you 馃槈
@anmonteiro cool thanks
I'm just testing namespace aliases with latest commit and noticed this ns
doesn't work anymore:
(ns metosin.core.async.debounce
#?(:cljs (:require-macros [cljs.core.async.macros :as a]))
(:require #?(:cljs [cljs.core.async :as a]
:clj [clojure.core.async :as a])))
It is giving error about missing a/go-loop
Is this is a known issue? Is it an issue, is using same alias for macros and regular requires valid? Should I create an issue?
@juhoteperi: first make it minimal to determine what鈥檚 actually going on
@juhoteperi: using the same alias for a macro ns and a runtime ns (when they are differently named), I鈥檓 pretty sure if that ever worked it was not intentional
still if there鈥檚 a simple way to recover that ok, if it clashes with the new enhancements - not going to support it
Hmm, okay. I'll create report with minimal code anyway to be sure
@juhoteperi: FWIW it鈥檚 also breaking for me with current master, and working fine in 1.9.89
But first I'll try to find a better way to write that which works
this is what I used:
(ns foo.core
(:require-macros [cljs.core.async.macros :as a])
(:require [cljs.core.async :as a]))
(let [c (a/chan)]
(a/go-loop [foo (a/<! c)]))
I also didn鈥檛 know this would work, also why I tried it just now by curiosity
I don't remember if I saw if somewhere or how I found it - but I have found it the easiest way to write cljc code using core.async
but I would still consider this super low priority and completely unintended and undefined
FWIW this is the commit that broke it: https://github.com/clojure/clojurescript/commit/41a62bfd916208d30bf621aefba56c5dce031ce5
@juhoteperi: I attached a patch to JIRA, can you confirm it fixes your issue? http://dev.clojure.org/jira/browse/CLJS-1716