This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2022-01-31
Channels
- # announcements (1)
- # aws (4)
- # babashka (40)
- # beginners (89)
- # calva (13)
- # cider (3)
- # clj-kondo (36)
- # cljdoc (16)
- # clojure (74)
- # clojure-boston (1)
- # clojure-dev (7)
- # clojure-europe (30)
- # clojure-new-zealand (1)
- # clojure-nl (17)
- # clojure-uk (5)
- # clojurescript (16)
- # core-async (9)
- # cursive (16)
- # datahike (3)
- # datalog (6)
- # datascript (7)
- # datomic (15)
- # emacs (38)
- # events (2)
- # figwheel-main (3)
- # fulcro (6)
- # google-cloud (18)
- # graalvm (6)
- # gratitude (1)
- # honeysql (1)
- # introduce-yourself (1)
- # jobs (1)
- # leiningen (5)
- # lsp (6)
- # malli (11)
- # meander (2)
- # off-topic (4)
- # re-frame (6)
- # reitit (8)
- # releases (2)
- # remote-jobs (3)
- # reveal (4)
- # shadow-cljs (200)
- # sql (8)
- # tools-deps (16)
I took a crack at a full implementation of specialized equality for concrete map, seems like I got about 2x speedups This is less a bump and more a question if I should pursue this further, submit a patch, etc, including what kind of tests you'd like to see. https://ask.clojure.org/index.php/11124/persistent-collections-implement-equiv-more-efficiently?show=11523
thx, I've been working towards that ask question this morning, was going to turn it into a ticket
I'm not sure yet. it's unclear to me where exactly you are proposing to make this change?
is this like for APersistentMap.equiv() and APersistentVector.doEquiv() ?
if you were to characterize the set of cases where things can be most improved, what is that set? I'm trying to figure out how more narrowly state the title of the ask question