This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-04-13
Channels
- # admin-announcements (2)
- # beginners (27)
- # boot (85)
- # cider (24)
- # cljs-dev (20)
- # cljsrn (16)
- # clojure (73)
- # clojure-brasil (2)
- # clojure-czech (152)
- # clojure-dusseldorf (7)
- # clojure-france (3)
- # clojure-japan (1)
- # clojure-norway (1)
- # clojure-poland (7)
- # clojure-russia (140)
- # clojure-uk (7)
- # clojurescript (66)
- # cursive (20)
- # datomic (8)
- # emacs (7)
- # events (1)
- # hoplon (325)
- # jobs (2)
- # jobs-discuss (69)
- # leiningen (3)
- # off-topic (6)
- # om (48)
- # onyx (82)
- # parinfer (1)
- # planck (10)
- # re-frame (53)
- # reagent (8)
- # ring (103)
- # untangled (13)
- # yada (14)
It is expected behavior that nodejs target code (compiled with :advanced
optimizations) with main function, does not receives the & args properly?
(defn main
[& [type]]
(cond
(= type "init")
(bench-init)
(= type "knn")
(bench-knn)
(= type "test")
(test-accuracity)
:else
(println "not implemented")))
(set! *main-cli-fn* main)
this code with :simple
optimizations works, but with :advanced
compilation the type
or & args
becomes nil
some peple claims that node also can benefits from advanced compilation and/or dead code elimination
maybe parsing time, I don't know, in any case I don't need it and I agree that :simple
is more than enough
I’ve yet to see anyone really demonstrate that parsing time really matters under Node.js
Any ETA for the next clojurescript release? I'd like to use parallel-build . Are there blocking issues that need help?
@dnolen: looks like @mfikes successfully tested this patch with Planck and in REPL. I also didn't notice any errors when building with Leiningen.
Are there any more cases where it makes sense to test the patch?
@dnolen @roman01la Also tested the patch with my personal projects and things worked as expected :thumbsup: