On 8/20/16, 7:13 PM, "Colin Fleming" <clojure@googlegroups.com on behalf of colin.mailingl...@gmail.com> wrote: > in this case it seems like the change breaks a lot of existing code
I disagree. Compared to the vast amount of Clojure code out there, I would contend that this breaks very little code – and that code is arguably wrong in the first place. Most of the handful of library maintainers that have been notified about this increase in strictness have been quick to fix their code (and mostly have been quick to release new versions). This has also been my experience so far for libraries that defined their own versions of one or more of the new predicates added in Clojure 1.9.0 – very quick updates to add the appropriate :exclude to :refer-clojure in those namespaces (and that was for a _warning_, not even an error!). > they have to wait for an update to the library, or fork it. Or stay on Clojure 1.8.0. Which is true of any other change in Clojure itself that causes breakage in code. I find it very interesting that, in the past we’ve often see relatively slow take up of the prerelease builds, with folks saying they don’t want to use prerelease software, yet for Clojure 1.9.0 we’re seeing much more uptake of clojure.spec driving early adoption of these builds. Sean -- 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.
