For the last month or so I've been working on completing Aaron Cohen's CinC.
As planned, this first period has been spent working extensively on the analyzer improving it to the point where it's competitive with the analysis done in Compiler.java while keeping it clojurescript-like and extensible via small composable passes over the AST [1]. There's some doc about the passes that are implemented and about the AST nodes produced at in the doc directory of the repository [2]. Notably, the jvm analyzer is able to propagate the tag of expressions to infer the tag of more complex expressions avoiding the necessity of explicit tagging in order to avoid run-time reflection in some cases. There are two "main" namespaces: `cinc.analyzer` and `cinc.analyzer.jvm`; the first one should not be used directly but should rather be extended to platform-specific forms and passes as done by `cinc.analyzer.jvm`. Work on the jvm emitter will start soon. Thanks, Nicola. [1] https://github.com/Bronsa/CinC/tree/analyzer-WIP/src/cinc/analyzer/passes [2] https://github.com/Bronsa/CinC/tree/analyzer-WIP/doc -- -- 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/groups/opt_out.