This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-08-10
Channels
- # admin-announcements (1)
- # alda (1)
- # bangalore-clj (1)
- # beginners (94)
- # boot (139)
- # braveandtrue (1)
- # cider (19)
- # cljs-dev (21)
- # cljsjs (8)
- # cljsrn (79)
- # clojure (124)
- # clojure-austin (1)
- # clojure-belgium (1)
- # clojure-berlin (3)
- # clojure-hamburg (3)
- # clojure-quebec (1)
- # clojure-russia (77)
- # clojure-spec (5)
- # clojure-uk (18)
- # clojurescript (39)
- # conf-proposals (21)
- # core-async (5)
- # cursive (8)
- # datomic (40)
- # defnpodcast (1)
- # devcards (14)
- # dirac (5)
- # editors (1)
- # emacs (4)
- # jobs (1)
- # liberator (4)
- # onyx (29)
- # perun (15)
- # proton (15)
- # protorepl (9)
- # re-frame (47)
- # reagent (38)
- # ring (1)
- # rum (7)
- # specter (23)
- # untangled (8)
- # yada (55)
While :use
is supported at the NS declaration level, REPLs only support import
and require
.
@dnolen: has this ever come up? worth creating a ticket to add support for use
in REPLs?
@anmonteiro: I think someone mentioned it before but I’ve been too lazy to implement it myself. Sure!
seems like a useful addition. I’ll create a ticket
@dnolen: worth adding use-macros
too, even though we have implicit macro inference now?
@anmonteiro: yeah for completeness that makes sense
@dnolen: OK it was incredibly easy to make this one work
assigned to you http://dev.clojure.org/jira/browse/CLJS-1729
@dnolen: playing around with this I remembered something else. With the support for :rename
now in place, shouldn’t we also support refer-clojure
at the REPL?
@anmonteiro: sure though I suspect people would use that one quite a bit less
@dnolen: agreed, definitely a very minor issue. I’ll create a ticket for completeness nevertheless
http://dev.clojure.org/jira/browse/CLJS-1715 @mfikes is this still relevant?
@richiardiandrea: http://dev.clojure.org/jira/browse/CLJS-1515 needs to be rebased
I’m going to see if I can fix CLJS-1731 as it’s important for ensuring the other bootstrapped tickets are OK to apply.
Ok I will do it
just added a FAQ section to cljs-zone: https://github.com/binaryage/cljs-zones#faq ideas/comments welcome, especially how to make it play well with core.async 🙂
The cljs.spec.test
macros namespace now employs eval
, which presents a challenge for bootstrapped ClojureScript: Since the namespace must be compiled as ClojureScript in that environment, an eval
would need to be fashioned for this purpose. I bet it can be done with a little work. I shake my fist at Alex 😜