This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-03-06
Channels
- # aleph (2)
- # arachne (4)
- # aws (3)
- # beginners (196)
- # cider (131)
- # cljs-dev (208)
- # clojure (193)
- # clojure-boston (1)
- # clojure-dev (26)
- # clojure-greece (4)
- # clojure-italy (26)
- # clojure-losangeles (1)
- # clojure-russia (11)
- # clojure-spec (40)
- # clojure-uk (78)
- # clojurescript (168)
- # cursive (25)
- # datascript (1)
- # datomic (31)
- # docker (8)
- # docs (1)
- # emacs (20)
- # fulcro (62)
- # hoplon (3)
- # jobs (1)
- # leiningen (3)
- # luminus (1)
- # nrepl (25)
- # off-topic (10)
- # other-languages (3)
- # parinfer (11)
- # planck (37)
- # portkey (54)
- # protorepl (11)
- # re-frame (2)
- # reagent (19)
- # remote-jobs (1)
- # ring (2)
- # rum (8)
- # shadow-cljs (23)
- # spacemacs (4)
- # uncomplicate (6)
- # unrepl (77)
- # vim (56)
- # yada (2)
I just saved 18kB in code size by adding a single pair of {}
. This is getting out of hand. We really need at least a warning for when sablono doesn't know if something is a map of attrs and decides to duplicate kilobytes of code.
@rauh: btw, I'm looking at hicada very closely — I'm hoping I will be able to use it to replace sablono.
Unfortunately, my app is rather large already, and I've become one of the more "stable" adopters at this point.
@jrychter you can hook into Sablono’s compilation defmulti and overwrite default method to not include interpret code at runtime
Yep, there’s no easy and safe way to get rid of interpretation once you got there