New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
cut does not treat <> in first slot as a function #185
Comments
I'm not sure this is what cut is supposed to do. It creates partially applied functions (that is, filling in arguments), you are not filling in arguments. This works:
Of course you know that... I'll have to think about it, but it doesn't make much sense when you can just write
|
I suppose it comes down to whether or not you want |
alternatively, I don't think <> should be allowed in the first slot |
I think I'll do what you suggested in the OP. This was modelled after SRFI 26 so I think we should have it compatible. I should also add the rest slot while at it. Or do you want to PR? |
Nah, my PR would just be the one line in the original post anyways. Go ahead |
This follows the Scheme SRFI 26 notation.
Done. Thanks for the idea. |
o/ |
For example
fails.
I suggest checking PARAMS and conditionally prepending funcall:
Edit: that would also mean small fixes to
-orfn
andandfn
The text was updated successfully, but these errors were encountered: