This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-12-26
Channels
- # adventofcode (23)
- # babashka (13)
- # beginners (63)
- # calva (17)
- # circleci (2)
- # cljdoc (3)
- # cljfx (11)
- # clojure (23)
- # clojure-europe (2)
- # clojure-uk (1)
- # conjure (1)
- # depstar (4)
- # emacs (3)
- # fulcro (41)
- # graalvm (29)
- # joker (5)
- # malli (6)
- # reagent (6)
- # reitit (1)
- # remote-jobs (1)
- # shadow-cljs (19)
- # spacemacs (8)
- # testing (9)
- # tools-deps (33)
What's the state of graalvm (20.3.0) and any clojure programs that do a requiring-resolve
?
@dharrigan requiring-resolve = require + resolve, both are problematic when used in a dynamic fashion. you should try to get rid of these and do require + resolve only on the top level (not in function bodies)
Thank you. Unfortunately, can't easily do that. I'm using juxt clip to manage some dependencies, and it uses requiring-resolve
they do work when you put a top-level require before those are executed (but they will lead to slightly more bloated binaries)
@dharrigan you want to execute clojure dynamically in a graalvm binary?
this is what I've made sci for: https://github.com/borkdude/sci
More like I have a system that uses juxt clip to manage injection of dependencies, like a database (connection), a kafka connection) etc..
clojure.core/eval
doesn't work in a graalvm binary, since it needs the Clojure compiler and dynamic classloading
Does that mean things like the component system by Stuart Sierra wouldn't work either?
@dharrigan it depends. :P
@dharrigan I don't see why it wouldn't work