This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-10-23
Channels
- # announcements (1)
- # babashka (29)
- # beginners (53)
- # berlin (1)
- # cider (14)
- # clj-kondo (18)
- # cljsrn (16)
- # clojure (141)
- # clojure-france (4)
- # clojure-italy (8)
- # clojure-norway (1)
- # clojure-uk (57)
- # core-async (7)
- # cursive (3)
- # data-science (2)
- # datomic (12)
- # duct (5)
- # fulcro (27)
- # hoplon (37)
- # immutant (1)
- # jobs (2)
- # jobs-discuss (7)
- # kaocha (2)
- # leiningen (3)
- # music (17)
- # nyc (1)
- # off-topic (22)
- # pathom (27)
- # re-frame (33)
- # reitit (23)
- # shadow-cljs (20)
- # tools-deps (15)
- # vim (29)
@dominicm the way I currently enable "interop" is by creating bindings like (.foo x)
where foo is a normal function which is set to #(.foo ^TheClass %)
https://github.com/SevereOverfl0w/high/#defining-a-system-configuration defining a system like so
the code is read using edamame which is configurable so it can read "normal" Clojure code: https://github.com/borkdude/edamame
@dominicm for the File
class this happens here:
https://github.com/borkdude/babashka/blob/master/src/babashka/impl/File.clj
How does babashka/sci know to route to this thing? Does it look at the metadata annotation? anyway, don't think this will work for me because I want to work with user-supplied memfns.
total aside, babashka makes me think of https://en.wikipedia.org/wiki/Baba_Yaga 🙂
babashka (with an a) also means a thing in Russian: it's an iron bar to connect spaces between words in typography
Oh, I tried googling babashka and didn't get anything except "granny" and pictures of you 🙂