On Sunday, August 21, 2016 at 5:25:03 PM UTC-5, Brian Marick wrote: > > As an update. I’ve fixed the `ns` oopsie in Suchwow (one file), and the > coincident `ns` oopsie in Midje (one file). But this happens when running > Midje’s self-tests against Clojure 1.9alpha11: > > > Exception in thread "main" java.lang.IllegalArgumentException: Call to > clojure.core/fn did not conform to spec: > > In: [0] val: clojure.core.unify/var-unify fails spec: > :clojure.core.specs/arg-list at: [:args :bs :arity-1 :args] predicate: > vector? > > In: [0] val: clojure.core.unify/var-unify fails spec: > :clojure.core.specs/args+body at: [:args :bs :arity-n] predicate: (cat > :args :clojure.core.specs/arg-list :prepost (? map?) :body (* any?)) > > :clojure.spec/args (clojure.core.unify/var-unify [varp v expr binds] > (clojure.core/if-let [vb__10124__auto__ (binds v)] > (clojure.core.unify/garner-unifiers varp vb__10124__auto__ expr binds) > (clojure.core/if-let [vexpr__10125__auto__ (clojure.core/and (varp expr) > (binds expr))] (clojure.core.unify/garner-unifiers varp v > vexpr__10125__auto__ binds) (if (clojure.core.unify/occurs? varp v expr > binds) (throw (java.lang.IllegalStateException. (clojure.core/str "Cycle > found in the path " expr))) (clojure.core.unify/bind-phase binds v > expr))))) > > , compiling:(clojure/core/unify.clj:82:18) > > I suspect the problem is that Midje uses an old version of > clojure.core.unify (0.5.2). I use that old version because a later versions > (like the current 0.5.7) failed in my use case for no reason I could > quickly understand.
Hard to help without more info. > So I decided to just stick with the older, working version because forced > upgrades make kittens suffer. And I am a kitten. And also: by semver I don't know that core.unify follows semver. I don't know that it doesn't, but that seems like an assumption. > , why should a satisfied user of 0.5.2 care about 0.5.7? > There is a change log: https://github.com/clojure/core.unify#change-log > (Note: I don’t know whether clojure.core.unify 0.5.7 is conformant to > whatever spec is breaking.) > It is. I released core.unify 0.5.7 about a month ago to fix the spec issue mentioned above. > > So upgrading Midje to Clojure 1.0alpha11 is not turning out as simple as > might be hoped. > > I know that, pace Casablanca[*], the problems of a guy trying to provide > an alternative to clojure.test don’t amount to a hill of beans in this > crazy world. But I offer this datapoint for clojure.core.team > consideration. > > ———— > > [*] > > Rick: But I've got a job to do, too. Where I'm going, you can't follow. > What I've got to do, you can't be any part of. Ilsa, I'm no good at being > noble, but it doesn't take much to see that the problems of three little > people don't amount to a hill of beans in this crazy world. Someday you'll > understand that. > [Ilsa lowers her head and begins to cry] > Rick: Now, now... > [Rick gently places his hand under her chin and raises it so their eyes > meet] > Rick: Here's looking at you kid. > > -- 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.
