This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-06-23
Channels
- # bangalore-clj (1)
- # beginners (23)
- # boot (90)
- # cljs-dev (133)
- # cljsrn (5)
- # clojure (104)
- # clojure-austin (1)
- # clojure-belgium (2)
- # clojure-dev (12)
- # clojure-gamedev (4)
- # clojure-italy (2)
- # clojure-russia (6)
- # clojure-spec (30)
- # clojure-uk (117)
- # clojurescript (197)
- # core-async (25)
- # cursive (9)
- # datomic (95)
- # devops (1)
- # dirac (49)
- # emacs (1)
- # hoplon (3)
- # immutant (10)
- # lein-figwheel (2)
- # luminus (5)
- # off-topic (43)
- # pedestal (1)
- # protorepl (1)
- # re-frame (13)
- # sql (5)
- # untangled (1)
actually, a smaller demo would be something that creates a proxy, runs a method on the proxy that does proxy super, and while the super method is running, does an update-proxy, when the super method return and the call to proxy-super completed it would clobber any changes made via update-proxy
I vaguely remember a bug related to this, but it wasn’t with proxy-super
- I believe it was when proxying a class whose super constructor calls a method on the object - that method is not initialised at that time.
I'm trying to debug code that is spending about 25% of the time sitting in: clojure.core$promise$reify__7005.deref()
. Any suggestions?
i.e. are you sure you're not spending 25% of your time waiting for the promise to be delivered?
I have a thread-local atom I use reset!
to preserve state. When I comment out the reset!
line it speeds up. Even if I reset!
to a constant it's slow.