This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-08
Channels
- # announcements (2)
- # aws (1)
- # beginners (134)
- # calva (26)
- # cider (48)
- # cljdoc (41)
- # cljs-dev (12)
- # clojure (178)
- # clojure-brasil (1)
- # clojure-europe (16)
- # clojure-italy (30)
- # clojure-nl (13)
- # clojure-spec (118)
- # clojure-uk (81)
- # clojurescript (209)
- # community-development (77)
- # cursive (7)
- # datomic (23)
- # duct (6)
- # emacs (15)
- # events (2)
- # figwheel (13)
- # figwheel-main (18)
- # fulcro (4)
- # jackdaw (4)
- # jobs (6)
- # jobs-discuss (6)
- # kaocha (2)
- # lein-figwheel (3)
- # off-topic (4)
- # other-languages (22)
- # pathom (2)
- # pedestal (9)
- # perun (10)
- # portkey (1)
- # re-frame (41)
- # reagent (6)
- # reitit (4)
- # remote-jobs (1)
- # ring-swagger (6)
- # rum (5)
- # shadow-cljs (300)
- # sql (3)
- # test-check (6)
- # testing (7)
- # vim (1)
- # yada (9)
There are some signs that there are some regressions in CLJS with regards to exceptions and spec? https://github.com/jeaye/orchestra/issues/41#issuecomment-461649942
there also seems to be a regression resulting in Can't take value of macro .
warnings https://clojurians.slack.com/archives/CALJ3BFLP/p1549456266299400
we’re also seeing this warning sometimes for cljs.core/exists?
, but I couldn’t repro it yet in a minimal example
That's the second time that I see this kind of when+and report on newer cljs. I think that is some optimization problem with type inference
@borkdude none yet, wasn’t sure if this is an actual cljs issue or if its tooling related
can you say how to reproduce it? which steps to take? I can do a quick check if it happens in shadow-cljs as well?
@thheller can’t reproduce it yet with specific set of steps. will report back when I can do so
The only hunch I have with respect to spurious analysis errors and Figwheel is https://github.com/bhauman/figwheel-core/pull/2