This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-09
Channels
- # aleph (4)
- # beginners (31)
- # boot (33)
- # cider (7)
- # cljs-dev (263)
- # cljsrn (1)
- # clojure (33)
- # clojure-austin (2)
- # clojure-dev (1)
- # clojure-russia (6)
- # clojure-spec (19)
- # clojure-uk (7)
- # clojurescript (79)
- # cursive (21)
- # datascript (1)
- # datomic (13)
- # dirac (12)
- # emacs (15)
- # hoplon (26)
- # lein-figwheel (3)
- # leiningen (1)
- # luminus (5)
- # lumo (20)
- # mount (1)
- # off-topic (17)
- # om (13)
- # onyx (24)
- # parinfer (70)
- # pedestal (2)
- # re-frame (19)
- # reagent (1)
- # ring-swagger (3)
- # unrepl (8)
- # untangled (58)
- # yada (2)
I wonder how much of a good idea would be to refactor a lib out of cider-nrepl
, exposing common repl functionality (like the brand new spec explorer)
@richiardiandrea I've been thinking about this too. cider-nrepl could be uh, cider? (and cider could be cider.el!).
https://github.com/tpope/vim-fireplace/pull/80 this was catching onto something similar via https://github.com/ctford/poker
The problem with macro-like destructuring is that you lose a lot: comments, formatting, various readers (discard, tagged, conditional), sets and maps original order is not preserved, numbers representations are lost (base N, ratios). Been there somehow done that.
wow, I actually did not know that nRepl
was the responsible of printing a lot of stuff: https://github.com/clojure-emacs/cider-nrepl/blob/master/src/cider/nrepl/print_method.clj
and TIL about MultiFn
@richiardiandrea originally that was an optional namespace.