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
A variadic argument may be quoted or evaluative (like any other argument).
If it is evaluative, then a TAKE that returned NULL could mean two things: either there was source material that evaluated to NULL -or- there was no more input to be gathered.
This inherent ambiguity suggests it's not clear that TAKE is a perfect operation for getting a variadic argument...or at least not one that is evaluative. The new behavior of EVAL(UATE) might be preferable, and restrict TAKE to quoted arguments only (though soft-quoted arguments straddle this definition).
In any case, these tests broke when TAKE was changed to return NULL without use of a special TAKE*:
A variadic argument may be quoted or evaluative (like any other argument).
If it is evaluative, then a TAKE that returned NULL could mean two things: either there was source material that evaluated to NULL -or- there was no more input to be gathered.
This inherent ambiguity suggests it's not clear that TAKE is a perfect operation for getting a variadic argument...or at least not one that is evaluative. The new behavior of EVAL(UATE) might be preferable, and restrict TAKE to quoted arguments only (though soft-quoted arguments straddle this definition).
In any case, these tests broke when TAKE was changed to return NULL without use of a special
TAKE*
:The issue requires some consideration. This consideration might mean that VARARGS! has distinct operators for dealing with it (?)
For now this test is commented out.
The text was updated successfully, but these errors were encountered: