This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-07-11
Channels
- # aws (15)
- # beginners (55)
- # boot (116)
- # bristol-clojurians (2)
- # cider (4)
- # cljs-dev (439)
- # cljsrn (14)
- # clojure (135)
- # clojure-argentina (3)
- # clojure-czech (4)
- # clojure-italy (60)
- # clojure-russia (1)
- # clojure-spec (48)
- # clojure-uk (42)
- # clojurescript (170)
- # cloverage (11)
- # core-async (19)
- # cursive (13)
- # datomic (48)
- # emacs (2)
- # graphql (3)
- # hoplon (8)
- # jobs (1)
- # jobs-discuss (5)
- # klipse (11)
- # luminus (5)
- # lumo (5)
- # mount (48)
- # off-topic (96)
- # om (17)
- # onyx (14)
- # parinfer (30)
- # protorepl (1)
- # re-frame (90)
- # reagent (2)
- # remote-jobs (1)
- # spacemacs (12)
- # specter (20)
- # uncomplicate (1)
- # untangled (65)
- # vim (2)
- # yada (8)
@onetom material web components
@flyboarder so i think the missing bit in my understanding is why using do-watch
causes a memory leak
@thedavidmeister im second guessing that, my previous understanding was that the -tpl macro was creating a new element when the cell updated, but if it works for the other attribute then perhaps it’s not creating a new element and my confusion is caused by :value
attribute
if it indeed is not creating a new element, then shouldn’t something like (cell= (and data value))
work? anytime the underlying data cell is updated, value should also update even if it hasn’t changed? However when I tested this I get the same result, so I believe the -tpl macro is creating a new element.
Could you roll the changes into your own value attribute? i think that would make it easier to test
@dm3 yeah so then it’s probably just the :value
attribute causing my confusion