Arc Forumnew | comments | leaders | submitlogin
8 points by pg 6151 days ago | link | parent

no:litmatch only works in functional position, because (no:litmatch ...) is transformed in ac into (no (litmatch ...)).

To add to the confusion, it's a bug that ~litmatch doesn't work in functional position. There's a comment reminding me to fix that in ac.scm.



1 point by parenthesis 6150 days ago | link

Wouldn't it make more sense for (~foo ...) to expand into (no (foo ...)) ?

-----

2 points by absz 6150 days ago | link

Not really, because that would make (keep ~foo lst) meaningless, and that's an important use of ~.

-----