This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-04-22
Channels
- # announcements (8)
- # babashka (4)
- # beginners (164)
- # calva (17)
- # cider (30)
- # cljdoc (4)
- # cljs-dev (6)
- # clojure (103)
- # clojure-europe (63)
- # clojure-nl (1)
- # clojure-norway (1)
- # clojure-portugal (1)
- # clojure-uk (3)
- # clojured (10)
- # clojuredesign-podcast (2)
- # clojurescript (16)
- # conjure (2)
- # core-async (9)
- # cursive (26)
- # datalevin (4)
- # datomic (156)
- # gratitude (1)
- # holy-lambda (8)
- # honeysql (9)
- # hoplon (6)
- # off-topic (55)
- # polylith (14)
- # portal (21)
- # reagent (5)
- # reitit (16)
- # releases (3)
- # shadow-cljs (87)
- # spacemacs (3)
- # tools-deps (25)
- # xtdb (9)
@huahaiy: is it ok if I try to implement https://github.com/juji-io/datalevin/issues/108 and provide a PR ? If that works well, I might work on providing the map interface as well.
We already have Iterable for these, just need to expose it properly, it is also possible to add reduce and map related interfaces to that as well. Since we have multiple modes (library, server, pods) and two bindings (java, graal), adding any public function will have to change many places. It would be difficult to do if one is not familiar with the code base. Of course, if you feel you are up to it, I am not against it. My suggestion is to enhance and expose iterate-kv
, and rename the existing one iterate-kv1
. The new one will return a type that implements IPersistentMap
. Please let me know if you want to take a crack on this. Thanks.