On Thursday, 6 September 2018 15:09:15 UTC+1, Andy Fingerhut wrote: > > > If you have a few minutes to try out the tests in my repo to see if you > get different results than I did, I'd be curious to hear if your results > are different. I'd be more curious to learn of a way to write a unit test > that gives the exception you see with Clojure 1.10.0-alpha7. > > Thanks for your help. I think I've made a mistake somewhere. I use emacs + CIDER and run the tests from there. With 'lein test' I don't see that error, but I do from emacs. So it may be something that's been updated in CIDER rather than clojure itself. I didn't realise they were different. The offending test was in a work project which has been put on hold/abandoned, but every time a new clojure comes out, I test it again to check it still works (ever hopeful it might be reinstated!). So, more had changed than just alpha6 to alpha7 when I tested this time.
Does that make sense? Peter -- 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.
