Very cool. If you think of other potential example errors this would be capable of detecting it might be nice to include them in a TODO list in the README. This might motivate someone to implement them or develop a nice emacs UI for displaying these errors.
Scott On Mon, Jan 2, 2012 at 4:14 AM, Ambrose Bonnaire-Sergeant < abonnaireserge...@gmail.com> wrote: > Inspired by the ClojureScript compiler, analyze is an interface to the > Clojure analysis phase. > > Check the README for some cool things you can do. > > https://clojars.org/analyze > https://github.com/frenchy64/analyze > > I've barely tested the library but it manages to analyze a good part of > the core Clojure library. > This is work in progress. > > If you heard Rich Hickey talking about leveraging the "analysis phase" at > the Conj, this is a step in that direction. > > Have fun :) > Ambrose > > -- > 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 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
