This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2017-11-28
Channels
- # adventofcode (2)
- # bangalore-clj (3)
- # beginners (171)
- # boot (28)
- # chestnut (3)
- # cljs-dev (20)
- # cljsjs (5)
- # clojure (280)
- # clojure-austin (1)
- # clojure-czech (1)
- # clojure-dev (9)
- # clojure-dusseldorf (2)
- # clojure-greece (20)
- # clojure-italy (6)
- # clojure-poland (16)
- # clojure-russia (7)
- # clojure-serbia (4)
- # clojure-sg (1)
- # clojure-spec (18)
- # clojure-uk (153)
- # clojurescript (57)
- # core-async (9)
- # cursive (21)
- # data-science (29)
- # datomic (18)
- # dirac (8)
- # docker (6)
- # duct (1)
- # emacs (50)
- # fulcro (15)
- # hoplon (56)
- # klipse (3)
- # leiningen (14)
- # lumo (1)
- # off-topic (5)
- # onyx (13)
- # other-languages (14)
- # pedestal (1)
- # perun (5)
- # planck (17)
- # re-frame (10)
- # reagent (2)
- # ring (1)
- # spacemacs (51)
- # sql (14)
- # test-check (16)
- # testing (1)
- # unrepl (93)
@qqq it looks like the functions you are calling need to set *ns*
for some reason, but you cannot set a dynamic var that has been creater in another thread. Probably the repl
task and that resolve
have to run inside the same pod, aka the pod of the repl
I think though there is a task already for reloading namespaces
Hi there, Reading this page https://github.com/boot-clj/boot/wiki/Pods I'm having a hard time figuring out when to use with-eval-in
or with-call-in
? Is there more documentation about pods somewhere?
Looking at the source code https://github.com/boot-clj/boot/blob/master/boot/pod/src/boot/pod.clj#L354 it seems that with-call-in
does the job of requiring the namespace whereas inside with-eval-in
you have to require it yourself
@U5UCAE37Z yes, I think that’s pretty much it.
should I add it in the wiki?
teawaterwire sure, thanks
To celebrate the release of Kotlin 1.2, which includes kotlin.test
, I've updated boot-kotlinc
to add a -t
/ --test
option to support easier testing: https://github.com/seancorfield/boot-kotlinc
@seancorfield nice! by the way, i've been meaning to ask you -- would you be interested in merging our boot kotlin efforts in some way? ( https://github.com/daveyarwood/boot-kotlin )
i think up until you added the test feature, our kotlin tasks have been roughly equivalent
@dave Ah, I didn't even know anyone else had built such a task...
Am I right that yours assumes resource-paths / source-paths are already set up? (by the command line or by the calling build.boot
file)
Based on whatever the user has already added to the paths?
no, the deps are hardcoded: https://github.com/daveyarwood/boot-kotlin/blob/master/src/io/djy/boot_kotlin.clj#L7-L11
(since it uses (core/input-files fileset)
)
I remember having several problems around handling of stdlib -- which is why I ended up explicitly adding that to the deps, rather than runtime and reflect. Was I just doing something dumb, perhaps?
I'm not actively using my project, except to tinker with Kotlin as I learn the language, so I'm happy to sunset mine in preference to yours. Feel free to incorporate any ideas from mine into yours. Are you using yours for production stuff? (or are both just tinkering? 🙂 )
i recently put kotlin in production, kinda-ish! good experience
(for a side project. started with dave's boot-kotlin, moved to maven to experience life as a full-on intellij weeny)
(side project is https://giftsforaprogrammer.com/, my kotlin program is basically a batch job that decorates a file of product asin's i have with latest pricing/image info)