This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-06-09
Channels
- # aleph (4)
- # arachne (3)
- # beginners (41)
- # boot (300)
- # cider (17)
- # cljs-dev (37)
- # cljsjs (4)
- # cljsrn (5)
- # clojure (249)
- # clojure-boston (3)
- # clojure-czech (4)
- # clojure-dev (14)
- # clojure-greece (183)
- # clojure-nl (2)
- # clojure-russia (11)
- # clojure-spec (135)
- # clojure-uk (37)
- # clojurescript (56)
- # community-development (8)
- # cursive (22)
- # data-science (4)
- # datomic (150)
- # devcards (6)
- # emacs (5)
- # euroclojure (8)
- # funcool (18)
- # hoplon (29)
- # immutant (1)
- # jobs (1)
- # lambdaisland (3)
- # lein-figwheel (7)
- # leiningen (18)
- # mount (1)
- # om (81)
- # onyx (95)
- # planck (50)
- # proton (6)
- # re-frame (62)
- # reagent (2)
- # ring (1)
- # robots (1)
- # spacemacs (2)
- # specter (88)
- # test-check (32)
- # untangled (23)
- # yada (1)
yep, you were right, at least it was a good exercise and I’ve learned a bit more while digging through it 🙂
it would be really handy if I could properly detect functions coming from cljs land, right now I have a heuristics which looks at name, but I cannot tell anything about single-arity anonymous functions, would be nice to have all cljs functions tagged with something like cljs$lang$type
or what about generating some specific name to all anonymous functions created by cljs?
devtools displays (anonymous function)
in call stack traces, it might be more helpful to generate some more descriptive name based on lexical context of those anon-fns
@dnolen: as discussed yesterday, i’ve started work performing benchmarks (found in cljs repo) and plotting them over releases. Initial work here: https://ducky427.github.io/clojurescript-benchmarks
will talk to some people tomorrow about how feasible it would be to have that be a part of our build process
as we are running those benchmarks on jsc as well, i guess they would need to be run on a mac
@rohit, and also the JavaScriptCore build for Linux is “apropos” in the sense that the ClojureScript unit test suite passes on it.
@dnolen: confirmed that the issue of serializing clojure.lang.Var
still exists on master. Adding a handler for clojure.lang.Var
does seem to resolve the issue but I’m not sure if my code is correct
@jr I don’t want to consider just wiring that in until I get more information about where this shows up in the analysis cache and how
explain {:name explain, :arglists ([this]), :doc “omitted", :protocol #'schema.core/Schema, :meta {:name explain, :arglists ([this]), :doc “omitted", :protocol #'schema.core/Schema, :file nil}
Nice @rohit, I was thinking about doing the same for code size
After reviewing the analyzer source code it seems that the :protocol
value in the analysis cache is expected to be a var. I put together a patch that deserializes the var in transit and works AFAICT
https://gist.github.com/JacobNinja/dd488daced80960c7ed5c547f4a39854
Is it acceptable to use a mies project to report a bug?