This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2023-03-09
Channels
- # announcements (4)
- # aws (3)
- # babashka (86)
- # babashka-sci-dev (31)
- # beginners (171)
- # biff (15)
- # calva (3)
- # clerk (47)
- # cljdoc (11)
- # clojure (59)
- # clojure-dev (11)
- # clojure-europe (122)
- # clojure-losangeles (1)
- # clojure-nl (2)
- # clojure-norway (4)
- # clojure-uk (2)
- # clojurescript (40)
- # cursive (5)
- # data-science (3)
- # datahike (1)
- # datomic (5)
- # fulcro (9)
- # graalvm (8)
- # hyperfiddle (17)
- # introduce-yourself (1)
- # java (28)
- # jobs (1)
- # malli (11)
- # membrane (9)
- # missionary (1)
- # nbb (1)
- # off-topic (5)
- # other-languages (1)
- # pedestal (1)
- # re-frame (4)
- # reagent (16)
- # releases (3)
- # remote-jobs (3)
- # shadow-cljs (83)
- # spacemacs (1)
- # sql (5)
- # tools-deps (28)
- # xtdb (15)
What's the status of work on the Java interop sugar around functional interfaces these days? @ghadi @alexmiller
I found https://clojure.atlassian.net/browse/CLJ-2637 but there were earlier issues too, yes?
I ask because the topic came up in a thread in #CBJ5CGE0G about a company rewriting a Clojure codebase to Java and someone said with the increase in use of functional interfaces in Java libraries, interop from Clojure was getting harder...
i sympathize that there is more use of functional interfaces in the wild than before, and that I'd like to see some sort of assistance in to core... ...that being said...
I don't buy that it is actually getting harder with the addition of functional interfaces, because when things were written in java without functional interfaces you got lots of bespoke interfaces for function like stuff, in both cases you have an interface (a Function or some bespoke project thing) and you just reify it
if anything java providing an official set of interfaces means you can write a single adapter from clojure fns to each of those and reuse those adapters everywhere
which is one of the options we're considering