Wishlist: for macros, metadata about the vars a macro will define. (E.g., (defmacro defrecord [...]) will define (->NAME arg...), (map->NAME m) when executed.)
This would allow a lot more source analysis for the common case of def* macros which are just fancy ways of def-ing vars, but without having to eval the macro. Maybe even without having to eval anything, if the mechanism is entirely declarative! This is an issue Colin Fleming (creator of Cursive) has talked about before, and I remember him saying something about creating such a mechanism for library authors to use for better Cursive integration. It'd be nice if such a mechanism could be standardized so the entire ecosystem could benefit. You should talk to him about this because he's given a fair amount of thought to this problem. On Monday, March 16, 2015 at 1:53:53 PM UTC-5, Christopher Medrela wrote: > > Hello! My name is Christopher Medrela and I'd like to work at "source > metadata > information model" project mentored by Alex Miller at Google Summer of > Code. I > hope that this mailing list is the right place to discuss such projects > (if I'm > wrong, correct me). > > I'd like to introduce some standard of source meta information model to > represent the code from the API perspective. There exist a lot of tools > like > codox, autodoc, Grimoire, ClojureDocs, crosscls.info and so on. Each of > these > tools has some repetitive code responsible for extracting this kind of > information. > > I'd like to discuss what the model should be and from which tasks you will > benefit most? You can find the model and tasks proposal in "model schema" > and > "tasks (deliverables)" sections in my [proposal] draft. I'd like to > emphasis > that the tasks list is very highly inspired by Alex Miller. > > [proposal] > https://gist.github.com/chrismedrela/6c9517c14ce1ca00062b#model-schema > -- 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.
