This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-26
Channels
- # announcements (4)
- # beginners (160)
- # boot (2)
- # calva (40)
- # cider (41)
- # clara (24)
- # cljdoc (2)
- # cljs-dev (99)
- # clojars (4)
- # clojure (71)
- # clojure-dev (9)
- # clojure-europe (4)
- # clojure-italy (2)
- # clojure-nl (19)
- # clojure-spec (97)
- # clojure-uk (103)
- # clojurescript (57)
- # core-logic (1)
- # cursive (15)
- # data-science (31)
- # datomic (24)
- # duct (1)
- # emacs (39)
- # events (7)
- # figwheel-main (14)
- # fulcro (44)
- # garden (7)
- # jobs (13)
- # juxt (1)
- # leiningen (29)
- # music (2)
- # nyc (4)
- # off-topic (37)
- # pathom (12)
- # re-frame (26)
- # ring (1)
- # ring-swagger (10)
- # shadow-cljs (35)
- # spacemacs (2)
- # specter (4)
- # test-check (67)
and welcome @hobosarefriends
Iām playing with an optimization for clojure.core/merge. In maps with lots of elements it can lead to a speedup of 1.23x
From December 1st to Christmas it happens a lot ;)
Hmm actually I haven't used a 2000 element map yet, even for aoc
2k elements is a lot, but it might happen if someone spouses the idea of namespaced maps i.p.v. nested maps. work from @U066U8JQJ on his graph stuff could lead to such cases. At Synple we had pretty big nested maps, if we were to use ns instead of nesting we would have probably reached a few hundred entries (not 2k tho)