Closed porky11 closed 6 years ago
Thanks for this. eval-macro-call
was added for unrelated reasons after this issue was submitted, and it handles the macroexpand
case. It only had to be modified slightly to handle the macroexpand-1
case, fortunately.
Especially the current way to see macroexpansions is not very usable. I'd like to be able to get the macro-expansion of a macro at compiletime, so I could write something like:
(print (macro-expansion (my-macro …)))
and see the expanded macro, maybe being able to specify a number of maximal expansions for recursive macros