On Monday, April 25, 2016 at 7:51:23 PM UTC-7, Matthew Butterick wrote: > FWIW the use case here is a problem I've come across in #lang building: > taking a parse tree produced by a reader and cleaning it up into a lovely, > cruft-free S-expression before passing it to the expander.
FWIW2, I've now worked out a `define-inverting-macro` form that behaves like `define-syntax` but will `local-expand` its arguments before pattern-matching them. So far this works quite nicely for processing parse trees, as it allows things to go in the logical order that would otherwise need to get yak-shaved. -- You received this message because you are subscribed to the Google Groups "Racket Users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
