This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-29
Channels
- # beginners (29)
- # boot (17)
- # calva (1)
- # cider (31)
- # cljs-dev (3)
- # clojure (169)
- # clojure-europe (1)
- # clojure-france (1)
- # clojure-russia (40)
- # clojure-serbia (3)
- # clojure-uk (42)
- # clojurescript (19)
- # clr (3)
- # core-async (7)
- # core-typed (3)
- # cursive (43)
- # datascript (4)
- # datomic (2)
- # dirac (4)
- # emacs (2)
- # fulcro (85)
- # funcool (1)
- # nrepl (5)
- # off-topic (14)
- # shadow-cljs (28)
- # spacemacs (5)
- # tools-deps (2)
are there any especially difficult obstacles for implementing an nrepl middleware for clojure-clr, perhaps providing something like what piggieback provides for clojurescript?
@vxe It’s mostly lack of interest and time. It’s doable, but given the fact that few people use CLR it’s not something high up on our to-do list. It also can’t be done the same way as it’s done for Piggieback, as you can’t drive the evaluation from a JVM, the same way you can do it for ClojureScript.
It would be most feasible to have a separate nREPL implementation for CLR or to use reader conditionals in the current implementation to support CLR.