This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-08-23
Channels
- # babashka (22)
- # beginners (8)
- # calva (7)
- # clj-kondo (65)
- # cljdoc (9)
- # cljsrn (1)
- # clojure (53)
- # clojure-australia (4)
- # clojure-europe (49)
- # clojure-gamedev (2)
- # clojure-italy (13)
- # clojure-nl (1)
- # clojure-spec (19)
- # clojure-uk (4)
- # clojurescript (48)
- # clojureverse-ops (1)
- # core-async (3)
- # css (2)
- # cursive (15)
- # datomic (6)
- # degree9 (2)
- # depstar (4)
- # emacs (2)
- # find-my-lib (1)
- # fulcro (16)
- # graalvm (11)
- # gratitude (1)
- # honeysql (9)
- # introduce-yourself (2)
- # jobs (1)
- # joker (2)
- # livestream (2)
- # malli (16)
- # nbb (4)
- # news-and-articles (2)
- # off-topic (1)
- # pathom (7)
- # polylith (10)
- # practicalli (1)
- # re-frame (7)
- # reitit (1)
- # releases (3)
- # remote-jobs (1)
- # rewrite-clj (19)
- # shadow-cljs (10)
- # tools-build (1)
- # tools-deps (9)
- # uncomplicate (1)
- # vim (3)
- # xtdb (44)
@deleted-user you mean Process.exec? If yes, should work
we need to use the interop with native functions for that, a maybe relevant example: https://gist.github.com/borkdude/335c9911cabf4db6d47cc772b4c69d4d#file-setenv-java-L23
I turned on *warn-on-reflection*
in all of my namespaces and fixed all of the reflections it warned me about. Now I'm wondering if I should turn it back off for production builds? Is there a performance impact in either graal native executables or JVM code at runtime if I leave it enabled everywhere?
no perf impact
affects whether a warning is emitted during compilation but you're doing the same work either way (and only once)
or rather, this is my generic Clojure answer, not sure if graal changes that but I doubt it
ok, makes sense. thanks alex!