This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2020-07-08
Channels
- # announcements (5)
- # aws (15)
- # babashka (7)
- # beginners (138)
- # bristol-clojurians (2)
- # chlorine-clover (11)
- # cider (9)
- # clara (4)
- # clj-kondo (17)
- # cljsrn (20)
- # clojars (1)
- # clojure (73)
- # clojure-europe (17)
- # clojure-italy (1)
- # clojure-nl (9)
- # clojure-spec (4)
- # clojure-uk (9)
- # clojurescript (43)
- # data-science (1)
- # datomic (87)
- # emacs (2)
- # figwheel-main (30)
- # fulcro (71)
- # helix (2)
- # hugsql (4)
- # jackdaw (5)
- # jobs (3)
- # jobs-discuss (31)
- # juxt (5)
- # kaocha (6)
- # lein-figwheel (16)
- # leiningen (1)
- # luminus (4)
- # malli (2)
- # meander (54)
- # music (8)
- # nrepl (12)
- # observability (28)
- # off-topic (85)
- # pathom (11)
- # re-frame (99)
- # reitit (9)
- # ring (1)
- # rum (6)
- # sci (11)
- # shadow-cljs (102)
- # sql (22)
- # tools-deps (10)
- # vim (65)
- # xtdb (14)
Hey, guess who’s till playing around with sci and rewrite-cljc? Yes, it is me! Because rewrite-cljc uses protocols to coerce from Clojure forms to rewrite-cljc nodes, it is a bit lower level than I’d like in a couple of cases for testing rewrite-cljc via sci.
So I don’t think I’d be able to test these two cases via sci interpreted rewrite-cljc tests.
Another area of interest for me is some rewrite-cljc tests use create-ns
. But I think I’m going to ignore those for the time being as I have an outstanding todo to review those tests.
@lee I think having a subset of your tests in graalvm is sufficient. At least you have an idea of what works and you don't get a compile time error with graalvm because of something
You could supplement the tests with some GraalVM smoke tests where you run some arbitrary code through rewrite-cljc and don't use clojure.test to verify the result
the so called command line tool approach that clj-kondo and babashka also use for testing