This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-05-08
Channels
- # announcements (5)
- # babashka (46)
- # beginners (206)
- # boot (1)
- # bristol-clojurians (1)
- # calva (9)
- # chlorine-clover (27)
- # cider (1)
- # clara (10)
- # clj-kondo (105)
- # cljsrn (2)
- # clojars (1)
- # clojure (104)
- # clojure-europe (6)
- # clojure-nl (2)
- # clojure-uk (18)
- # clojurescript (44)
- # conjure (10)
- # core-async (34)
- # cursive (28)
- # data-science (6)
- # datomic (14)
- # emacs (44)
- # events (1)
- # figwheel-main (1)
- # fulcro (13)
- # graphql (9)
- # helix (12)
- # kaocha (2)
- # meander (4)
- # off-topic (2)
- # pathom (1)
- # quil (1)
- # re-frame (21)
- # shadow-cljs (49)
- # spacemacs (6)
- # xtdb (8)
saw redbush mentioned in #vim -- there's this piece for bencode in rust: https://github.com/jasilven/redbush/blob/master/src/nrepl/bencode.rs
but the code is very boilerplatey. I wonder if it can be made nicer with the serde crate
I would like to make spire also a pod. Without needing a separate binary build. could there be a way to have babashka launch the existing bin with and arg, say spire --pod
?
@retrogradeorbit I think something like this https://gist.github.com/jeroenvandijk/b63bc62ea150ec1969edb5dfd0754e0e Almost works :thinking_face:
You would wrap your spire binary with some babashka wrapper code. I think something goes wrong in the return value
No. Spier itself can behave as a pod. Pods can declare their namespaces to babashka. No need to create a wrapper or other binary
I think so. Iโm a bit lost in the protocol. But Iโm guessing this should be possible
Iโm very new to this too. I was just trying something ๐
The pod-babashka-hsqldb might be the best example since itโs more defensive and propagates exceptions to babashka
Updated the hsqldb + clj-kondo example here to use the pod-babashka-hsqldb pod: https://github.com/borkdude/babashka/blob/master/doc/examples.md#find-unused-vars
Maybe we can add some syntactic sugar as metadata in the ns form for loading pods... On second thought. Probably too much magic for now.
Not sure about this metadata magic yet. Cc @U0502D2GL
babashka.pods/load-pod would already be incompatible with clojure (unless I release babashka.pods as a library for the JVM, which might be a good idea)
The above is just adding some metadata on the namespace btw. It's not incompatible with Clojure, you can add any metadata on any namespace.
I agree that it might be a good idea to make babashka.pods a library that can be used in the jvm
I think it might be too much for now. I'll just abandon the idea until someone brings it up again
It's just that it's nice to have all namespace requires into one ns
form and pods kind of break that
oh, I'm sorry, I meant that adding the "feature" of making a separate babashka.pods lib and making it compatible with clojure was feature creep