Since spec is mainly a dependency of 1.9. to improve error reporting over 
1.8 (correct me if I'm wrong), I'd like to point out this ticket 
again: https://dev.clojure.org/jira/browse/CLJ-2013

It solves what I determined the root cause of this report 
https://groups.google.com/d/msg/clojure/mIlKaOiujlo/6b0So2siCgAJ which 
triggered a lengthy discussion at the time.

Also, the standard error reporter should sort problems by depth (length) of 
part as a default.

Thanks for looking into it,
 Leon.

On Thursday, September 28, 2017 at 4:00:16 PM UTC+2, stuart....@gmail.com 
wrote:
>
> Clojure 1.9 has been quite stable throughout the alpha period, and we now 
> hope to release after a very short beta. Please test your existing programs 
> on the latest beta (see below), and respond on this thread ASAP if you 
> discover anything you believe to be a regression.
>
> Thanks!
> Stu
>
> ;; Clojure deps.edn
> org.clojure/clojure {:mvn/version "1.9.0-beta1"}
>
> ;; lein & boot
> [org.clojure/clojure "1.9.0-beta1"]
>
>

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to clojure@googlegroups.com
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
clojure+unsubscr...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to clojure+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to