This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-02-01
Channels
- # announcements (11)
- # babashka (71)
- # beginners (34)
- # calva (25)
- # chlorine-clover (38)
- # cider (13)
- # clj-kondo (1)
- # cljsrn (2)
- # clojure (40)
- # clojure-australia (4)
- # clojure-europe (16)
- # clojure-france (3)
- # clojure-nl (4)
- # clojure-uk (16)
- # clojurescript (27)
- # conjure (2)
- # core-async (41)
- # core-logic (3)
- # cursive (1)
- # data-science (1)
- # datomic (16)
- # depstar (19)
- # emacs (7)
- # fulcro (33)
- # graalvm (4)
- # honeysql (20)
- # hugsql (4)
- # jobs (1)
- # juxt (4)
- # off-topic (48)
- # pathom (41)
- # reagent (9)
- # reitit (19)
- # remote-jobs (1)
- # shadow-cljs (20)
- # startup-in-a-month (2)
- # tools-deps (29)
- # vim (3)
- # xtdb (30)
I took a brief look at the nREPL issue mentioned in the PR. It looks like it might be fairly easy to get nREPL to compile into a native image. I'm not sure how useful that'd be to you guys, though, since actually using the nREPL native image to evaluate things is probably impossible, right?
that's right, we use it for developer, like make changes on clojure-lsp and check if they worked, but AFAIK even if it compiles correctly, it wouldn't work evaluating things after the image was already compiled
I took a brief look at the nREPL issue mentioned in the PR. It looks like it might be fairly easy to get nREPL to compile into a native image. I'm not sure how useful that'd be to you guys, though, since actually using the nREPL native image to evaluate things is probably impossible, right?