I don't know if this is a fruitful avenue to pursue, but the Eastwood lint
tool [1] uses tools.reader to read Clojure code, and the tools.analyzer
library to analyze it, while expanding all macros.
If someone can figure out a way to scan through the Abstract Syntax Tree
output of tools.analyzer to
I ran into a case today where I mistyped the keyword in a `keys` spec and
was surprised that validation was not catching invalid data. For my
purposes, it would be sufficient to have a automated test that looks at my
specs and identifies typos in the spirit of
https://gist.github.com/stuarthall
No, this is an excellent idea.
Joe Armstrong is probably the most notable modern figure to have written
and talked about making code content-addressable, with chunks of code (I
forget the granularity he proposed, probably top-levels?) having names as
metadata. IIRC, first at https://www.youtube
* https://github.com/philoskim/debux
* https://clojars.org/philoskim/debux
--
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 patien
On 12/06/2017 02:59 PM, Clojure beginner wrote:
Hi all
I heard about Clojure a week ago and have a new assignment at work to learn,
develope and deploy to production. I haven't developed in 2 years. Programming
background is: mainframe and informatica. I have bought 5 books: and Clojure
progra
