This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-01-16
Channels
- # beginners (115)
- # boot (13)
- # boot-dev (13)
- # chestnut (1)
- # cider (1)
- # clara (10)
- # cljs-dev (21)
- # cljsjs (1)
- # cljsrn (2)
- # clojure (120)
- # clojure-dusseldorf (2)
- # clojure-greece (13)
- # clojure-ireland (1)
- # clojure-italy (3)
- # clojure-nlp (3)
- # clojure-russia (2)
- # clojure-spec (13)
- # clojure-uk (82)
- # clojured (5)
- # clojurescript (47)
- # core-async (2)
- # core-logic (8)
- # cursive (45)
- # datomic (2)
- # editors (1)
- # emacs (39)
- # fulcro (166)
- # graphql (1)
- # hoplon (16)
- # keechma (5)
- # off-topic (202)
- # perun (4)
- # protorepl (7)
- # re-frame (28)
- # reagent (13)
- # ring (27)
- # ring-swagger (16)
- # rum (1)
- # shadow-cljs (25)
- # spacemacs (20)
- # sql (141)
- # yada (4)
I think racket is the only other major immutable-by-default lisp
I’m evaluating something like this in a pod:
(pod/with-eval-in my-pod
(->> (doall (#'codox.main/read-namespaces ~cdx-config))
(mapv cljdoc.grimoire-helpers/sanitize-cdx)))
codox.main/read-namespaces
uses println
to print some diagnostics when excluding vars — for some reason parts of this message show up sprinkled across the return value of with-eval-in
If I disable any exclusion and ensure that nothing is printed this way it works fine
I tried various macros to suppress output but none seemed to be working
Issue with repro created: https://github.com/boot-clj/boot/issues/683
I ran this command boot -d com.ingres.jdbc/iijdbc -d org.clojure/java.jdbc repl
to add those dependencies to the REPL, but how do I use them?
@josmith2016 You will need to require the namespaces using something like (require '[clojure.java.jdbc :as jdbc])
(untested)
Why does boot have to serialize exceptions? I run into cases using boot-cljs where I get non-serializable exceptions based on something I'm throwing from a macro.
@dave.dixon because Exceptions don't travel across pod boundaries, so you've got to serialize and deserialize them in order to pass them from one task to the other
Might be helpful to have the offending exception printed by the task if it turns out to be non-serializable. Otherwise it's impossible to figure out what the problem is.
@dave.dixon may be worth an issue to boot-cljs
there was also some more talking around this in the boot
issues