This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-07-06
Channels
- # aws-lambda (8)
- # beginners (49)
- # boot (13)
- # braveandtrue (2)
- # cider (12)
- # cljs-dev (15)
- # cljsrn (2)
- # clojure (143)
- # clojure-italy (8)
- # clojure-nl (17)
- # clojure-spec (22)
- # clojure-uk (21)
- # clojurescript (145)
- # code-reviews (1)
- # cursive (33)
- # data-science (14)
- # datomic (25)
- # emacs (3)
- # events (1)
- # fulcro (48)
- # graphql (1)
- # onyx (15)
- # perun (5)
- # play-clj (2)
- # protorepl (1)
- # re-frame (27)
- # remote-jobs (3)
- # ring (3)
- # rum (7)
- # shadow-cljs (87)
- # specter (4)
- # test-check (14)
- # testing (2)
- # tools-deps (9)
suppose you do not have a fixed (literal) path for things like setval, transform, etc. So, you have something like (transform [ATOM (apply keypath ks)] inc db)
. Does the 'This macro will do inline compilation and caching of the path.' still apply in this sort of situation? If not, is it still comparable in performance to update-in?
@jsa-aerial since ks
is not static, you pay the cost of the apply
and the keypath
expansion on every invocation
not sure how it will compare to update-in
but there will be a noticeable performance hit