Most helpful would be to know what Clojure version you are on now and what changed between when it didn't fail and when it did.
There have been a variety of changes to both type hints and classloading over the last few releases and it's likely that the error is now simply found when it was silently not found and ignored before. On Monday, January 23, 2017 at 3:01:38 PM UTC-6, William Parker wrote: > > I have a case where JVM Clojure code like (some-> ^JavaClassA this > ^FieldTypeA (.getFieldTypeA) (.getFieldTypeB)) previously compiled for a > long time and suddenly just started failing in our CI system because the > class FieldTypeA wasn’t imported in the namespace. I understand the need > to import the class but I don’t see why it ever compiled and am wondering > if there is any known nondeterminism here. I looked through the Clojure > JIRA tracker but didn't find anything that seemed related. > -- 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.
