On Mon, Mar 16, 2015 at 1:01 PM, Fluid Dynamics <a2093...@trbvm.com> wrote:
> On Monday, March 16, 2015 at 11:23:14 AM UTC-4, David Nolen wrote: >> >> Need more information. But that warning is most certainly not something >> emitted by the ClojureScript compiler. >> >> Make sure you can reproduce without whatever downstream tooling you may >> be using: https://github.com/clojure/clojurescript/wiki/Reporting-Issues >> >> There's a good chance it's purely downstream and needs to be reported >> elsewhere. >> > > The only thing the OP changed was the version of cljs he was using, and > his project went from working to broken. This means that one of the changes > in the new cljs broke something. Whether it directly broke the OP's code, > or broke a library that the OP's project depends on, is immaterial; the > location of the breaking change was in cljs itself > No. A surprising amount of downstream tooling relies on unpublished and undocumented details of the ClojureScript compiler. This kind of third party breakage is rarely if ever under consideration. David -- 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.
