Thank you for providing this extension, Richard. (And thank you, Hongwei, for being the prime-mover genius of all this; this is like watching Mozart write his symphonies.)
Is it intended that all extensions of Xanadu be placed at the same software-architectural design points as this extension? Or are there intended to be quite different categories of extensions that are placed in Xanadu's compiler at quite different software-architectural put-stuff-here design points—i.e., “horses for courses” as the British say: different horses are bred for different events/venues? (I am aware of Hongwei's posting in recent days regarding AST-to-AST-to-…-to-AST transforms as a key microkernel-esque breakthrough design of Xanadu. Those transforms/ASTs might be part of the answer, but are their more intended put-stuff-here design points?) On Saturday, December 21, 2019 at 3:09:53 AM UTC-6, Richard wrote: > > Here is an other extension example https://github.com/sparverius/xjsonize. > (see the readme for building instructions) > Outputs the AST at each transition level in json. This can be helpful for > writing other extensions or even just to learn ast. > -- You received this message because you are subscribed to the Google Groups "ats-lang-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to ats-lang-users+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/ats-lang-users/179ab5ea-4c65-4ef4-a6a4-35e988fb5e1d%40googlegroups.com.
