I migrated a significant Clojure codebase to 1.8.0-beta1, and I had to solve issues caused by this IMapEntry/APersistentVector change in several places (including the pull request mentioned above). Also wondering about the rationale behind this. It's not a huge deal, but it does make some code ambiguous (if you have a function that potentially accepts any object, including vectors of 2 elements, and you want to do something specific for instances of IMapEntry).
I didn't have any other problems apart from this - and I was actually migrating from clojure 1.6.0. Great job! Le jeudi 15 octobre 2015 16:28:16 UTC-7, Mike Rodriguez a écrit : > > Someone else looked at the issue on > https://github.com/ztellman/riddley/issues/18 > > This issue makes the current version of riddley, and therefore potemkin, > not work on Clojure 1.8 beta1 > > There is a pull request to fix it at > https://github.com/ztellman/riddley/pull/19 > > However I am wondering if it is going to affect more places. The problem > is that in Clojuee 1.8 APersistentVector now implements IMapEntry > (therefore j.u.Map$Entry as well), but it doesn't implement the key or val > methods. > What is the reason for that change and/or is this a desired side effect of > the change? > > -- 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.
