This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-02-26
Channels
- # aws-lambda (2)
- # beginners (10)
- # boot (17)
- # cider (19)
- # clara (1)
- # cljs-dev (13)
- # cljsjs (22)
- # cljsrn (1)
- # clojure (132)
- # clojure-austin (2)
- # clojure-berlin (2)
- # clojure-dusseldorf (1)
- # clojure-germany (2)
- # clojure-italy (7)
- # clojure-spec (6)
- # clojure-uk (5)
- # clojurescript (45)
- # core-matrix (3)
- # cursive (4)
- # datomic (8)
- # emacs (3)
- # keechma (3)
- # lein-figwheel (1)
- # leiningen (2)
- # lumo (24)
- # nyc (1)
- # off-topic (29)
- # om (68)
- # onyx (5)
- # perun (50)
- # planck (5)
- # protorepl (5)
- # re-frame (128)
- # reagent (10)
- # remote-jobs (1)
- # ring (4)
- # rum (41)
- # untangled (28)
- # yada (4)
`
(deftask touch-file [fname]
(fn [next-handler]
(fn [fileset]
(clojure.java.shell/sh "touch" fname)
@qqq Tasks have complete CLI parsing built-in — they are not exactly “just functions” 🙂
@seancorfield: yeah, it all makes sense in 2020 hindsight
does the design of boot arbitrarly decide I can not have functions with more than 52 arguments?
when dealing with cljs in boot; what controls the creation of the "main.out" and the "out" directories?
can I run two boots from the same directory, one with optimizations none and one with optimizations advanced? or will the two clobber each other due to things like .nrepl-port ?