This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-17
Channels
- # announcements (2)
- # aws (44)
- # beginners (96)
- # calva (10)
- # cider (7)
- # cljdoc (5)
- # cljsrn (2)
- # clojure (38)
- # clojure-dev (19)
- # clojure-europe (6)
- # clojure-italy (16)
- # clojure-nl (10)
- # clojure-norway (44)
- # clojure-spec (7)
- # clojure-uk (74)
- # clojurescript (133)
- # cloverage (1)
- # cursive (54)
- # datomic (78)
- # duct (11)
- # graalvm (5)
- # instaparse (4)
- # joker (3)
- # kaocha (5)
- # nrepl (2)
- # off-topic (10)
- # pathom (56)
- # pedestal (1)
- # reagent (7)
- # reitit (17)
- # shadow-cljs (144)
- # slack-help (2)
- # sql (35)
- # testing (5)
- # tools-deps (22)
- # vim (22)
- # xtdb (11)
If I organised a meetup about Graal and Clojure in London (hopefully recorded) what specific topics would be useful to cover. There definitely seems interest, but trying to figure out what to do. I am talking to one of the developers from Oracle who is interested in talking to us or doing a hackathon / clojure hacking with Graal event.
there are two parts to Graal: the polyglot part and the native part. So you could focus on either or both. The native part has some caveats with Clojure 1.10.1 which are possible to work around, but it might be good to be aware of that before the hackathon starts
Mostly related to https://clojure.atlassian.net/browse/CLJ-1472
As long as you don't load namespaces that require locking (like clojure.server or clojure.spec) it should be fine
if you haven't already, it would be nice if you upvoted https://ask.clojure.org/index.php/740/locking-macro-fails-bytecode-verification-native-runtime if you're interested in getting this fixed