This page is not created by, affiliated with, or supported by Slack Technologies, Inc.
2018-12-19
Channels
- # adventofcode (44)
- # announcements (2)
- # aws (9)
- # beginners (166)
- # braveandtrue (16)
- # calva (170)
- # cider (14)
- # cljdoc (9)
- # cljs-dev (4)
- # cljsrn (1)
- # clojars (1)
- # clojure (150)
- # clojure-dev (15)
- # clojure-europe (4)
- # clojure-india (3)
- # clojure-italy (93)
- # clojure-nl (18)
- # clojure-serbia (1)
- # clojure-spec (5)
- # clojure-uk (45)
- # clojurescript (54)
- # cursive (19)
- # data-science (8)
- # datomic (83)
- # emacs (6)
- # events (1)
- # hoplon (3)
- # hyperfiddle (3)
- # jobs (6)
- # jobs-discuss (1)
- # klipse (1)
- # lein-figwheel (6)
- # leiningen (15)
- # lumo (1)
- # nrepl (1)
- # pedestal (15)
- # re-frame (48)
- # reagent (4)
- # reitit (2)
- # remote-jobs (1)
- # rum (2)
- # shadow-cljs (111)
- # spacemacs (10)
- # sql (16)
- # testing (10)
- # tools-deps (5)
I'm confused about the error message improvements in 1.10... (let [x]) produces
Syntax error macroexpanding clojure.core/let at (form-init1640041536431823190.clj:1:1).
[x] - failed: even-number-of-forms? at: [:bindings] spec: :clojure.core.specs.alpha/bindings
and 1.8 produces:
IllegalArgumentException let requires an even number of forms in binding vector in scratchapp.core:1 clojure.core/let (core.clj:4333)
1.8 seems much more noob friendly/clear... what am I not understanding?Is this the "error messages got worse so they could get better" conversation that's been happening in the community later?
In that macro errors are more easily machine consumable, but the printing of their values became less beginner friendly in the interim?
I'm not sure there is much CIDER can/should do here. But i do believe that some of the error messages were hand tailored in older Clojures and these have been removed in favor of the current approach. I think there is a very informative ticket in jira that you should read and then if you still have questions you can chat with alex. although this was a ton of work and was just released two days ago so it may not be the best time to bring up things
I'm for sure am really grateful for all the work in this area and in no way am intending to say it's better or worse... I am just getting familiarized with things, and @futuro’s mention of 'more easily machine consumable' is probably what's going on.
I'm guessing the new error messages are going to be more more amenable to being integrated with things that will really explain things better to the user.
I think expound being integrated directly into cider would be a big win. It's an idea I've been thinking about for a while.
what is the current strategy for getting rid of the WARNING: clj-refactor and refactor-nrepl are out of sync.
message?
I have these in my dependencies:
[cider/cider-nrepl "0.18.0"]
[refactor-nrepl "2.4.0"]
although the error message shows Their versions are 2.4.0 (package: 20180826.2149) and n/a, respectively.
(cljr--version)
"2.4.0 (package: 20180826.2149)"
(cljr-version)
"clj-refactor 2.4.0 (package: 20180826.2149), refactor-nrepl is unreachable"
and what is the jack in command that CIDER issued? you can find this in the *Messages*
buffer (if you're not familiar)
@dpsutton nvm, I got it. I deleted the clj-refactor cache and restarted emacs