Why can Snap! macros not be hygienic?

In the reference manual, there is a reference to Scheme’s macro feature, stating how Snap! has had unevaluated inputs but not a way to separate the namespaces of the variables of a macro and its caller. Could hygienic macros not be created by having a block modify the expansion’s variable names and decode them when called?

Thank you.

Yes, that's totally doable, and is just waiting for me to get a:tuit:. The thing is, while I'm at it, I'd like to implement the pattern-matching part of Scheme macros (syntax-rules). So I have to work up a lot of energy.

Feel free to take this on as a project!

Thank you! I might attempt it after the custom types test.