3 ms·
From 'Let Over Lambda': These solutions try to limit or eliminate the impact of unwanted variable capture but unfortunately do so at the expense of wanted, des
by giantdude 4y ago
From 'Let Over Lambda':
These solutions try to limit or eliminate the impact of unwanted variable capture but unfortunately do so at the expense of wanted, desirable variable capture. Almost all approaches taken to reducing the impact of variable capture serve only to reduce what you can do with defmacro. Hygienic macros are, in the best of situations, a beginner's safety guard-rail; in the worst of situations they form an electric fence, trapping their victims in a sanitised, capture-safe prison. Furthermore, recent research has shown that hygienic macro systems like those specified by various Scheme revisions can still be vulnerable to many interesting capture problems
- PaulHoule 4y agoI have been playing around with a scheme for syntactic macros in Java where the macros are written in a very lispy way (from static imports) and one thing I noticed is that with namespaces, classes, and methods that code is always generated in, namespace collisions aren’t the hellish problem they are in Flat-namespaces LISP variants.