- 01 Oct, 2021 1 commit
-
-
Marius Gerbershagen authored
The test would succeed only the first time it was run, since it was creating a temporary directory each run which wasn't cleaned up.
-
- 15 Feb, 2021 1 commit
-
-
Marius Gerbershagen authored
-
- 17 Jan, 2021 2 commits
-
-
Raymond Toy authored
Use char-equal in position as indicted by phoe See merge request !45
-
-
- 03 Jan, 2021 2 commits
-
-
Raymond Toy authored
Fix Spelling error *unexpected-successes Closes #30 See merge request !44
-
Karsten Poeck authored
-
- 02 Dec, 2020 1 commit
-
-
Daniel Kochmański authored
Clear unexpected failures and successes See merge request !42
-
- 24 Nov, 2020 1 commit
-
-
Raymond Toy authored
Need to clear `*unexpected-failures*` and `*unexpected-successes* when running the test so that these variables contain the correct values. If we don't, then subsequent calls to run tests may indicate no unexpected results but these contain non-null values because a previous run set them.
-
- 23 Aug, 2020 1 commit
-
-
Marius Gerbershagen authored
loop8: add a test for destructuring bind See merge request !40
-
- 14 Aug, 2020 2 commits
-
-
Daniel Kochmański authored
Correct call to format in with-package-iterator.12 and with-package-iterator.13 Closes #27 See merge request !39
-
Daniel Kochmański authored
6.1.1.7 Destructuring states Destructuring allows binding of a set of variables to a corresponding set of values anywhere that a value can normally be bound to a single variable. During loop expansion, each variable in the variable list is matched with the values in the values list. If there are more variables in the variable list than there are values in the values list, the remaining variables are given a value of nil. If there are more values than variables listed, the extra values are discarded. These tests check, whether loop accepts destructuring bindings where there is less values than variables.
-
- 13 Aug, 2020 1 commit
-
-
Marius Gerbershagen authored
-
- 24 May, 2020 1 commit
-
-
Karsten Poeck authored
-
- 10 May, 2020 1 commit
-
-
Marius Gerbershagen authored
Add cases for same key, but values which are not equalp.
-
- 31 Dec, 2019 1 commit
-
-
Daniel Kochmański authored
Cleanup for error test cases in CLHS 22.3.5.2 See merge request !37
-
- 30 Dec, 2019 1 commit
-
-
Marius Gerbershagen authored
Fix PRINT-STRUCTURE.1 See merge request !36
-
- 26 Dec, 2019 1 commit
-
-
Marius Gerbershagen authored
Add SUBTYPEP.CONS.44 See merge request !30
-
- 20 Dec, 2019 2 commits
-
-
Marius Gerbershagen authored
-
Marius Gerbershagen authored
Having all of them at the same place makes them easier to find.
-
- 26 Nov, 2019 3 commits
-
-
Daniel Kochmański authored
Make char-equality in FORMAT-E tests case-insensitive See merge request !32
-
Daniel Kochmański authored
Add more cases to FORMAT.F.46 See merge request !34
-
This ensures that 0.01 is printed the same way - as ".0" for ~2f, ~1f, and ~0f.
-
- 25 Nov, 2019 1 commit
-
-
Michał Herda authored
With print escaping turned off, symbols are printed without any package prefix. The test called READ-FROM-STRING within WITH-STANDARD-IO-SYNTAX, which caused the resulting symbol to be read and interned within the CL-USER package. This commit fixes this behaviour (the symbol is interned in the CL-TEST package).
-
- 21 Nov, 2019 2 commits
-
-
Daniel Kochmański authored
Comment FORMAT.F.45 See merge request !33
-
Add a comment explaining the rationale for FORMAT.F.45 and why it is correct.
-
- 20 Nov, 2019 1 commit
-
-
Michał Herda authored
With ~E formatting, the exponent marker can be printed either in upcase or downcase - the standard does not specify the concrete case and allows both. Therefore string-equality for float numbers printed via ~E should use {STRING,CHAR}-EQUAL rather than {STRING,CHAR}=. This commit introduces this change.
-
- 19 Nov, 2019 10 commits
-
-
Daniel Kochmański authored
Fix upgraded-array-element-type.lsp See merge request ansi-test/ansi-test!31
-
Michał Herda authored
The comment in 1b8a8157 was not formatted properly and broke the build.
-
Daniel Kochmański authored
Add note :NO-FLOATING-POINT-UNDERFLOW-BY-DEFAULT See merge request ansi-test/ansi-test!29
-
Michał Herda authored
This note assumes that the implementation purposefully does not conform to 12.1.4.3 by not signaling FLOATING-POINT-UNDERFLOW by default. (The implementation should have an option of toggling this behaviour off in order to be able to signal this condition when underflows occur.) A reason for lack of conformance might be contradictory wording in the spec: 12.1.4.3 mentions that the errors should be signaled, while arithmetic operations mention that they "might signal" the error. Tests EXP{T,}.{8,9,10,11} have been annotated with this note.
-
Daniel Kochmański authored
Fix DEFSETF.7A Closes #19 See merge request ansi-test/ansi-test!25
-
Daniel Kochmański authored
Update upgraded-array-element-type.lsp See merge request ansi-test/ansi-test!27
-
Daniel Kochmański authored
Fix READTABLE-CASE.CASE tests Closes #20 and #21 See merge request !26
-
Daniel Kochmański authored
Annotate some LOOP tests with ANSI-SPEC-PROBLEM Closes #14 See merge request ansi-test/ansi-test!23
-
Daniel Kochmański authored
Comment out READ-SUPPRESS.17 Closes #18 See merge request ansi-test/ansi-test!24
-
Michał Herda authored
We add a SUBTYPEP test that checks SUBTYPEP relationship for CONS types with SATISFIES types in their CARs and CDRs. Whether t1 is a subtype of t2 depends on a series of RANDOM calls at typechecking time - sometimes it might be a subtype, it might not. This test is added because I see SBCL and CCL failures in this case. In addition to the test, we define four functions named subtypep.cons.44.{foo,bar,baz,qux}. This is because the CLHS states that the type specifier SATISFIES "denotes the set of all objects that satisfy the predicate PREDICATE-NAME, which must be a symbol whose global function definition is a one-argument predicate."
-
- 16 Nov, 2019 1 commit
-
-
Added comment explaining the (tricky) rationale behind upgraded-array-element-type.nil.1.
-
- 15 Nov, 2019 3 commits
-
-
Michał Herda authored
This fixes the symbol-interning issues that might have occured when `READ-FROM-STRING` was internally called in the wrong package. This also fixes the fact that the test names had no home package.
-
Michał Herda authored
-
Michał Herda authored
-