This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2019-02-06
Channels
- # adventofcode (1)
- # aleph (9)
- # announcements (22)
- # beginners (59)
- # boot (8)
- # calva (1)
- # cljdoc (7)
- # cljs-dev (10)
- # cljsrn (9)
- # clojars (10)
- # clojure (23)
- # clojure-dev (6)
- # clojure-europe (3)
- # clojure-italy (26)
- # clojure-nl (3)
- # clojure-seattle (1)
- # clojure-spec (46)
- # clojure-uk (85)
- # clojurescript (97)
- # core-async (13)
- # cursive (3)
- # data-science (10)
- # datomic (156)
- # duct (34)
- # emacs (37)
- # figwheel (3)
- # figwheel-main (9)
- # fulcro (59)
- # hyperfiddle (4)
- # immutant (1)
- # jackdaw (3)
- # jobs (1)
- # off-topic (112)
- # parinfer (1)
- # qlkit (2)
- # re-frame (1)
- # reagent (35)
- # ring-swagger (2)
- # shadow-cljs (104)
- # spacemacs (9)
- # speculative (12)
- # tools-deps (30)
- # yada (10)
question, does expound
work with 1.10.516
? I have a comment in my sources that it does not with 1.10.439
well I can definitely try it out (sorry lazy question here 😄)
1.10.439 didn’t work with expound only if you were trying to use expound for macro-expansion or instrumentation
I haven’t tried it with 1.10.516, but my guess is that all the recent great work to port over the way errors are handled will fix the issue
If you use expound for anything else, both versions should work, please open a bug if 1.10.516 doesn’t work.
yeah I am using it for instrumentation - so will open issues, thanks for the update!
I noticed I created a duplicate for CLJS-2844 here:
https://dev.clojure.org/jira/browse/CLJS-3049
I thought it wasn’t implemented because I did something wrong in the REPL myself (you first have to unstrument something before the undef becomes effective).
When looking into the code of CLJS-2844, I noticed that there isn’t special handling of nil
here:
https://github.com/clojure/clojurescript/blob/master/src/main/cljs/cljs/spec/alpha.cljc#L71
This has the result that after undefining a spec, it’s still present in the result of (stest/checkable-syms)
.
So, I think I’ll rename the issue to address this.