This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2021-05-05
Channels
- # announcements (7)
- # babashka (61)
- # beginners (146)
- # cider (4)
- # clj-kondo (25)
- # cljsrn (29)
- # clojars (30)
- # clojure (30)
- # clojure-australia (17)
- # clojure-europe (43)
- # clojure-italy (16)
- # clojure-nl (2)
- # clojure-spec (13)
- # clojure-sweden (7)
- # clojure-uk (8)
- # clojurescript (38)
- # cursive (12)
- # datomic (42)
- # defnpodcast (2)
- # dirac (1)
- # events (5)
- # fulcro (5)
- # graalvm (43)
- # graphql (11)
- # helix (6)
- # jackdaw (13)
- # jobs (4)
- # lambdaisland (8)
- # malli (12)
- # off-topic (83)
- # pathom (9)
- # podcasts-discuss (2)
- # re-frame (6)
- # reagent (3)
- # reitit (8)
- # remote-jobs (1)
- # shadow-cljs (40)
- # vim (21)
clojure-mode 5.13 is out! The release features a few small improvements https://github.com/clojure-emacs/clojure-mode/releases/tag/5.13.0
toggle-ignore
, hmm… Someone asked for a command helping with ignores quickly in Calva, but we agreed that typing alt+left
, #_
was quick enough (the first keypress there moves the cursor to the start of the form). But now, looking at the changelog for this update… I see a toggle-ignore-surrounding-form
and it starts to make more sense.
Announcing clojure-graalvm-agent-helper to ease native configuration generation for native-image tool. https://github.com/FieryCod/clojure-graalvm-agent-helper
com.github.seancorfield/next.jdbc {:mvn/version "1.2.659"}
— The next generation of clojure.java.jdbc
: a new low-level Clojure wrapper for JDBC-based access to databases. — The main difference from 1.1.646 (and the reason for 1.2.x) is that clj-commons/camel-snake-kebab
is now an unconditional dependency, rather than a conditional one, which improves GraalVM-native compatibility and removes some potential edge cases when trying to use the library in certain multi-artifact projects. https://cljdoc.org/d/com.github.seancorfield/next.jdbc/1.2.659/doc/getting-started Follow up in #sql Thanks to @snorremd for additional PostgreSQL-related docs and @delaguardo for help getting GraalVM testing up and running!
It is possible to make dependencies conditional and make them compatible with GraalVM native-image. I would say this could even improve native-image compatibility by leaving out deps that don't play well with it (and reduce binary size) but do it the right way: only resolve at compile time (top level) and not at runtime (function body). https://github.com/yogthos/Selmer/blob/master/src/selmer/tags.clj#L392-L403
But it seems you were already doing this correctly, so I don't understand why this change makes it better for GraalVM. Anyway, it's great that you are considering support for it :thumbsup:
I was running into problems with it in our multi-artifact monorepo at times and I just sort of got tired of working around it. I also wasn’t 100% sure I was doing it correctly, conditionally, for use with GraalVM-native so I figured I should just remove the “at times”/uncertainty and be done with it. Lots of next.jdbc
users seem to want the snake/kebab conversions anyway (and it’s not like next.jdbc
doesn’t already depend on other libs — I’m a bit surprised the java.data
dependency/code doesn’t cause GraalVM-native issues…?).