- Dec 29, 2023
-
-
Robert Goldman authored
Explain where iterate is being maintained and update the current version number.
-
- Dec 17, 2022
-
-
Robert Goldman authored
-
Robert Goldman authored
Making the whitespace canonical going forward.
-
Robert Goldman authored
This is only used in Allegro, and Duane Rettig tells me it's unnecessary even there. For now I have just patched it, rather than trying to remove it.
-
Robert Goldman authored
This will allow us to merge fixes with greater confidence going forward.
-
- Dec 08, 2021
-
-
Robert Goldman authored
-
Robert Goldman authored
Previously if a test failed upstream of running the actual tests, CI would not notice because we weren't check for it. This obscured test failures on several lisps.
-
Robert Goldman authored
-
Robert Goldman authored
Create a package for DEPRECATION-WARNING to live in, so that it does not inadvertently cause pain for programmers who `use` the `iterate` package. Package has nickname `ITERATE-WARNINGS`.
-
- Dec 03, 2021
-
-
Robert Goldman authored
For some reason, ECL cannot successfully load the iterate/tests system as a side-effect of running ASDF:TEST-OP on it. It gets a package error if it tries. I suspect this is an ECL bug. This patch works around it.
-
Robert Goldman authored
Previously there was code in here to recreate an RCS (!) repository for RT. Removed this.
-
Robert Goldman authored
Don't allow the tests to pass if the build fails. This seems to have been possible before.
-
Robert Goldman authored
The report-string for the DEPRECATION-WARNING condition had a spurious "~2:*" in it that caused Clozure CL to (correctly) error out.
-
- Aug 20, 2021
-
-
Phoebe Goldman authored
this better matches previous behavior when RESULT-TYPE is not supplied.
-
- Aug 19, 2021
-
-
Phoebe Goldman authored
incl. minimal documentation and a pair of tests
-
Phoebe Goldman authored
-
Phoebe Goldman authored
-
- May 23, 2021
-
-
Robert Goldman authored
-
Robert Goldman authored
-
Robert Goldman authored
-
Robert Goldman authored
Also replace use of `count` with `counting` in other tests.
-
Robert Goldman authored
-
Robert Goldman authored
This isn't really configured properly, either. Need to investigate further.
-
Robert Goldman authored
The use of count, which hijacks a function definition in the CL package, violates a design principle articulated in the manual and paper. Instead, only "counting" should be supported. When a program uses COUNT in the context of ITERATE, this will emit a deprecation warning. The intent is to remove support for COUNT as a synonym for COUNTING in the next version of ITERATE.
-
- May 19, 2021
-
-
Robert Goldman authored
-
Robert Goldman authored
-
- May 18, 2021
-
-
Control flow clauses that return from an iterate form without executing the epilogue code (e.g. `never` and `leave`) currently do so by expanding into `(return-from ,*block-name*)`. For iterate forms without a user-provided name, the block will be named `nil`. This causes problems when used with other Common Lisp looping constructs such as `dolist`: (iterate (for i :from 0 :below 10) (dolist (x '(5 10 15)) (never (= i x)))) ; => T, but should be NIL This patch adds a separate `*loop-name*` variable that will be bound to a gensym for `NIL`-named blocks and makes the various epilogue-skipping code refer to that instead of `*block-name*`. Iterate forms *without* an explicit user-provided name will still have a separate `(block nil ...)` wrapping so users can still `(return ...)` as before. Before (simplified): (iterate (leave)) ; ==> (block nil (return-from nil)) (iterate foo (leave)) ; ==> (block foo (return-from nil)) After: (iterate (leave)) ; ==> (block nil (block #:ITERATE123 (return-from #:ITERATE123))) (iterate foo (leave)) ; ==> (block foo (return-from foo))
-
- May 17, 2021
-
-
Robert Goldman authored
There are enough fixes for me to call this a bugfix release.
-
Robert Goldman authored
-
Robert Goldman authored
In some contexts, ITERATE could incorrectly warn that it is assigning a default initial value of `NIL`. Here we filter out cases where supplying `NIL` is fine, and no warning should be raised.
-
Robert Goldman authored
A spurious warning is generated by ITERATE when adding a type declaration for driver variables. This is caught by test `type.8`.
-
Robert Goldman authored
There was a cut-and-paste typo in this test.
-
- Feb 03, 2021
-
-
- May 11, 2020
-
-
On unmodified version of iterate on CCL this test will fail.
-
Avoids unnecessary compiler warnings when using on Clozure Common Lisp.
-
- Jan 25, 2020
-
-
Breanndán Ó Nualláin authored
-
Breanndán Ó Nualláin authored
Previously the following code would fail since S was closed after the first ITER. (progn (iter (for line in-stream s) (for n below 2)) (iter (for line in-stream s) (for n below 2)))
-
- Feb 07, 2018
-
-
Attila Lendvai authored
Ignore-this: 417350676e91e6f6d7f41f64a7ad0b7e darcs-hash:987ecc38fa3a940db9285c036a1f11fdf64771d1
-
- Jan 23, 2018
-
-
Attila Lendvai authored
Ignore-this: 47c28331db5d7aa76625078f3ff5f9bb darcs-hash:8e3164ce4db2468289cd426aa8a791d809df62ea
-
- Jan 16, 2018
-
-
Attila Lendvai authored
Ignore-this: 4d63abf412919ed8b4dac0b285ddd678 reported and fixed by Ilya Perminov <iperminov@dwavesys.com>. darcs-hash:dc32a60ff626a15db2fcb187f43a7dc7225c3f35
-