You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We've got function literals in the form of lambdas, and macros are essentially a first-class object in Blueprint anyway, so maybe we should add a syntax to create anonymous macros?
The text was updated successfully, but these errors were encountered:
Definitely fexpr, since we renamed macro → fexpr in c3e7a8a.
A new question: suppose we implement fexpr literals and use fexpr to create them. Should we use fun instead of lambda to create function literals to match the defun/deffexpr symmetry?
We've got function literals in the form of lambdas, and macros are essentially a first-class object in Blueprint anyway, so maybe we should add a syntax to create anonymous macros?
The text was updated successfully, but these errors were encountered: