This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-04-21
Channels
- # aws (1)
- # aws-lambda (1)
- # beginners (27)
- # boot (16)
- # cider (1)
- # clara (54)
- # cljs-dev (4)
- # cljsjs (8)
- # cljsrn (25)
- # clojure (148)
- # clojure-dev (2)
- # clojure-finland (1)
- # clojure-france (18)
- # clojure-italy (10)
- # clojure-nl (3)
- # clojure-russia (27)
- # clojure-sg (2)
- # clojure-uk (17)
- # clojurebridge (6)
- # clojurescript (70)
- # core-async (1)
- # css (6)
- # cursive (35)
- # data-science (3)
- # datomic (22)
- # events (4)
- # jobs (18)
- # jobs-discuss (14)
- # leiningen (4)
- # lumo (22)
- # off-topic (20)
- # om (5)
- # om-next (1)
- # onyx (47)
- # pedestal (107)
- # re-frame (43)
- # reagent (1)
- # ring (2)
- # ring-swagger (2)
- # rum (18)
- # sql (15)
- # unrepl (4)
- # vim (61)
- # yada (3)
😀 big thanks to everyone who worked on externs inference… I’ve used it in a couple of projects now and got the hang of it, it’s really helpful!
I’m looking into adding a cljs compatibility layer to refactor-nrepl
which mainly involves working with the cljs analyzer and replicating some searches on the ast -- the current version uses tools.analyzer.jvm
for clojure code.
One thing I seem to be missing is the end-line/column
values in the nodes’ env. It seems only a few nodes carry that information, while on the other hand tools.analyzer adds it much more frequently and a lot of refactor-nrepl relies on that data to match a cursor position to an AST location.