This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-09-25
Channels
- # bangalore-clj (1)
- # beginners (13)
- # boot (163)
- # cljsrn (23)
- # clojure (70)
- # clojure-czech (1)
- # clojure-russia (6)
- # clojure-spec (8)
- # clojurescript (47)
- # cloverage (16)
- # cursive (2)
- # editors (1)
- # garden (2)
- # lein-figwheel (1)
- # om (30)
- # om-next (2)
- # perun (2)
- # planck (23)
- # rdf (4)
- # reagent (1)
- # specter (2)
- # untangled (8)
- # vim (7)
(ns foo.bar
(:require
[planck.core :refer [line-seq *command-line-args*]]
[]
[cljs-time.coerce :as t]
[cljs-time.format :as tf]
[cljs-time.core :as time]))
$ time planck -c/Users/matthew/.m2/repository/com/andrewmcveigh/cljs-time/0.4.0/cljs-time-0.4.0.jar test.cljs
planck test.cljs 6.96s user 0.27s system 134% cpu 5.355 total
That takes ~7s on my macbook pro.@mnewhook Interested in what happens if you add -K
or -k <path>
and run it twice (once to create cache and again to use it)
I had already tried the cache but I didn鈥檛 realize you had to use -K to actually use the cache 馃檪
FWIW I like that cache is opt-in, as it could swallow e.g. undeclared var errors when using Planck aggressively at development time
so it definitely depends on the use case. So far it doesn鈥檛 bother me to specify -K
or -`k`whenever I want it to use caching
e.g.: planck -Kc <classpath goes here>
is not troublesome at all!
(There are some bugs regarding cache like https://github.com/mfikes/planck/issues/227 and https://github.com/mfikes/planck/issues/293)
@mfikes could #293 be related to a corrupted cache?
I think there was a fix in the CLJS compiler for that
on the JVM side, ofc
perhaps it could be more obvious in the documentation that -K is also necessary to use the cache. > The first time you run Planck this way, it will save the results of compilation into .planck_cache. Then subsequent executions will use the cached results instead. Perhaps instead: The first time you run Planck this way, it will save the results of compilation into .planck_cache. Then subsequent executions with -K will use the cached results instead.