3 ms·
Breaks how? I'm on my phone, not a computer right now and can't test, but that should call the CL function - ITERATE uses `counting` for that particular operati
by shawn_w 1y ago
Breaks how? I'm on my phone, not a computer right now and can't test, but that should call the CL function - ITERATE uses `counting` for that particular operation to avoid conflicts; see https://iterate.common-lisp.dev/doc/Gathering-Clauses.html https://iterate.common-lisp.dev/doc/Gathering-Clauses.html
Or is the documentation wrong?
- Jtsummers 1y agoApparently this is a quicklisp problem, they haven't updated the release since 2021 when it was still broken.
- shawn_w 1y agoI just grabbed the latest ITERATE source off of its gitlab repository, and, yeah, that bit is still giving an error: Iterate, in (COUNT I SOME-SEQUENCE): Missing value for SOME-SEQUENCE keyword as well as WARNING: COUNT appears to be used as an ITERATE clause keyword, in this sexpression: (COUNT I SOME-SEQUENCE). This use is now deprecated and will cease to be supported in a future version. Please use the alternative keyword COUNTING instead. If you intended COUNT to be interpreted as a function call, instead of an ITERATE clause, you must find an alternative way of calling it, at present, perhaps by using FUNCALL or APPLY. Have to use (iter (for i from 1 to 10) (print (funcall #'count i some-sequence))) Guess the documentation /is/ wrong (for now, until the code finishes catching up)
- Jtsummers 1y agoWell, some-sequence was obviously an example, you'd have to fill it in with an actual sequence. Put in '(1 2 3) instead or assign something to it. But yeah, that's still not something I intend to use if they make you work around what should be plain Common Lisp.
- shawn_w 1y agoI had a some-sequence variable defined. (Using a literal list or vector gives a different error)