This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-09-19
Channels
- # announcements (1)
- # babashka (40)
- # beginners (84)
- # biff (46)
- # calva (37)
- # cherry (2)
- # cider (18)
- # clj-otel (5)
- # clojure (53)
- # clojure-europe (39)
- # clojure-hungary (12)
- # clojure-norway (40)
- # clojure-sweden (2)
- # clojure-uk (2)
- # clojurescript (6)
- # community-development (21)
- # cursive (28)
- # data-science (12)
- # datomic (3)
- # figwheel-main (2)
- # fulcro (12)
- # graalvm (7)
- # gratitude (1)
- # hyperfiddle (23)
- # integrant (9)
- # jobs (2)
- # leiningen (4)
- # lsp (8)
- # malli (3)
- # missionary (1)
- # off-topic (39)
- # polylith (3)
- # portal (33)
- # practicalli (4)
- # re-frame (3)
- # releases (1)
- # sci (53)
- # solo-full-stack (8)
- # sql (5)
- # timbre (9)
GraalVM for JDK 21 released: https://www.graalvm.org/release-notes/JDK_21/ https://medium.com/graalvm/graalvm-for-jdk-21-is-here-ee01177dd12d
Hmmm.... from medium blog: > In this release, we are introducing a https://github.com/oracle/graal/pull/4684 that will become the default in the future: all classes are now allowed to be used and initialized at build time, regardless of the class initialization configuration Will have to understand if this impacts/helps/whatevers our graal-build-time work. Seems experimental at this point, so probably no immediate action is needed.
Are you afraid it will break something? Or are you considering whether it will enable new possibilities for clojure-compiled-to-native, because then we can do some stuff compile time, before it gets โfrozenโ?