Clojurians Log v2

@borkdude, before I explore your idea further of testing rewrite-cljc under GraalVM > so how it works with babashka: you include the library like the other built-in libraries. and then you run the unit tests from source with bb I vaguely remember you having to get CircleCI to bump available RAM to native-image babashka… am I remembering correctly?

@lee Are you hitting a limit?

@lee A couple of things to try: - Set BABASHKA_XMX to -J-Xmx3500m or something like that and pray it compiles - Disable all feature flags to eliminate libraries you don't need - Use sci instead of bb for trying this out. The only other ns you'll need to incorporate is clojure.test, you can copy that code from babashka. The latter could also serve as a template for testing other libs in GraalVM

Or: ask @marc-omorain to bump your memory limit. Or use Github actions, not CircleCI to compile.

I think PRs against babashka should compile with 8GB though, so making a WIP PR against babashka should also work

Not hitting a limit, just getting an understanding of constraints before digging in. Thanks for all the ideas and tips!

@lee awesome, good to hear! That repo contains some code to watch clojars and send PRs to Repos that might need project.clj updates. We're about to release that to the community, along with a few other tools that people will hopefully find useful. One for formatting https://go.atomist.com/catalog/skills/atomist/cljfmt-skill and one for adding clj-kondo https://go.atomist.com/catalog/skills/atomist/clj-kondo-skill are almost ready to go (speaking of rewrite-clj!)

I'm excited to start using rewrite-cljc when it's ready

cool! I’ll announce when rewrite-cljc is up on clojars. It is open source, so... not sure when, but it’ll get there.