announcements

Project/library announcements ONLY - use threaded replies for discussions. Do not cross post here from other channels. Consider #events or #news-and-articles for other announcements.
bozhidar 2021-05-05T13:32:39.122500Z

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

๐Ÿ‘ 4
6
4
๐Ÿš€ 8
๐ŸŽ‰ 10
Karol Wรณjcik 2021-05-05T14:01:06.124Z

Announcing clojure-graalvm-agent-helper to ease native configuration generation for native-image tool. https://github.com/FieryCod/clojure-graalvm-agent-helper

๐ŸŽ‰ 10
pez 2021-05-05T15:00:14.125300Z

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.

seancorfield 2021-05-05T20:15:29.130800Z

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!

๐Ÿ‘ 18
1
1
๐ŸŽ‰ 4
borkdude 2021-05-05T22:52:31.132200Z

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

borkdude 2021-05-05T22:58:00.132900Z

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: