This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2016-12-21
Channels
- # beginners (201)
- # boot (125)
- # cider (3)
- # cljs-dev (21)
- # cljsrn (165)
- # clojars (8)
- # clojure (332)
- # clojure-belgium (1)
- # clojure-gamedev (8)
- # clojure-russia (75)
- # clojure-spec (25)
- # clojure-uk (96)
- # clojurebridge (2)
- # clojurescript (130)
- # code-reviews (16)
- # cursive (26)
- # datomic (20)
- # devops (6)
- # emacs (6)
- # hoplon (90)
- # jobs (9)
- # luminus (2)
- # off-topic (4)
- # om (65)
- # onyx (5)
- # pedestal (4)
- # protorepl (6)
- # re-frame (34)
- # reagent (12)
- # ring (4)
- # ring-swagger (7)
- # specter (2)
- # test-check (8)
- # untangled (2)
- # vim (1)
- # yada (6)
is it normal for lein test
to fail some tests? https://travis-ci.org/frenchy64/clojurescript
@ambrosebs I think the official way to run tests is via ./script/test
and others
lein test
is supposed to pass
script/test
tests the CLJS part, lein test
tests the compiler infrastructure (in Clojure)
@ambrosebs FWIW current master passes lein test
@ambrosebs lein test
should work
thanks. I was going to prefer if-some/some?/when-some over that idiom. Is that still a win?
@ambrosebs they weren’t until I inlined some?
which hasn’t landed in a release yet
I see. Can I do a pass over analyzer.clj and clean up the (not (nil? )) into some?
, since I'm hacking there anyway? Plenty of opportunities for (let [e ..] (if (not (nil? e))) => (if-some [e ..] ) also.
@ambrosebs yes now that it inlines thats fine, but should be in a standalone patch that can be applied quickly for the obvious reasons