X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=tests%2Ftype.impure.lisp;h=da143e3828af0c4289d608716c9a8951eafae2b1;hb=25e76ec2b1083ac6a4bba42af7ad7b5a8239f2b8;hp=effe4a05edd6671c37e7ef361a316af20fff9eab;hpb=3b45a7b66afe95080562d266dd447b1286abece0;p=sbcl.git diff --git a/tests/type.impure.lisp b/tests/type.impure.lisp index effe4a0..da143e3 100644 --- a/tests/type.impure.lisp +++ b/tests/type.impure.lisp @@ -1,6 +1,16 @@ -(in-package :cl-user) +;;;; This software is part of the SBCL system. See the README file for +;;;; more information. +;;;; +;;;; While most of SBCL is derived from the CMU CL system, the test +;;;; files (like this one) were written from scratch after the fork +;;;; from CMU CL. +;;;; +;;;; This software is in the public domain and is provided with +;;;; absolutely no warranty. See the COPYING and CREDITS files for +;;;; more information. (load "assertoid.lisp") +(use-package "ASSERTOID") (defmacro assert-nil-nil (expr) `(assert (equal '(nil nil) (multiple-value-list ,expr)))) @@ -9,16 +19,21 @@ (defmacro assert-t-t (expr) `(assert (equal '(t t) (multiple-value-list ,expr)))) +(defmacro assert-t-t-or-uncertain (expr) + `(assert (let ((list (multiple-value-list ,expr))) + (or (equal '(nil nil) list) + (equal '(t t) list))))) + (let ((types '(character integer fixnum (integer 0 10) single-float (single-float -1.0 1.0) (single-float 0.1) (real 4 8) (real -1 7) (real 2 11) + null symbol keyword (member #\a #\b #\c) (member 1 #\a) (member 3.0 3.3) - ;; FIXME: When bug 91 is fixed, add these to the list: - ;; (INTEGER -1 1) - ;; UNSIGNED-BYTE - ;; (RATIONAL -1 7) (RATIONAL -2 4) - ;; RATIO + (integer -1 1) + unsigned-byte + (rational -1 7) (rational -2 4) + ratio ))) (dolist (i types) (format t "type I=~S~%" i) @@ -57,6 +72,11 @@ (assert (type-evidently-= '(integer 0 10) '(or (integer 0 5) (integer 4 10)))) +;;; Bug 50(c,d): numeric types with empty ranges should be NIL +(assert (type-evidently-= 'nil '(integer (0) (0)))) +(assert (type-evidently-= 'nil '(rational (0) (0)))) +(assert (type-evidently-= 'nil '(float (0.0) (0.0)))) + ;;; sbcl-0.6.10 did (UPGRADED-ARRAY-ELEMENT-TYPE 'SOME-UNDEF-TYPE)=>T ;;; and (UPGRADED-COMPLEX-PART-TYPE 'SOME-UNDEF-TYPE)=>T. (assert (raises-error? (upgraded-array-element-type 'some-undef-type))) @@ -70,10 +90,10 @@ ;;; part I: TYPEP (assert (typep #(11) '(simple-array t 1))) (assert (typep #(11) '(simple-array (or integer symbol) 1))) -;;; FIXME: broken by 0.pre7.15 #!-SB-INTERPRETER stuff -#+nil (assert (raises-error? (typep #(11) '(simple-array undef-type 1)))) +(assert (raises-error? (typep #(11) '(simple-array undef-type 1)))) (assert (not (typep 11 '(simple-array undef-type 1)))) ;;; part II: SUBTYPEP + (assert (subtypep '(vector some-undef-type) 'vector)) (assert (not (subtypep '(vector some-undef-type) 'integer))) (assert-nil-nil (subtypep 'utype-1 'utype-2)) @@ -82,7 +102,7 @@ (assert-nil-nil (subtypep '(vector t) '(vector utype-2))) ;;; ANSI specifically disallows bare AND and OR symbols as type specs. -#| ; Alas, this is part of bug 10, still unfixed as of sbcl-0.6.11.10. +#| ; Alas, this is part of bug 10, still unfixed as of sbcl-0.7.2. (assert (raises-error? (typep 11 'and))) (assert (raises-error? (typep 11 'or))) |# @@ -97,13 +117,89 @@ (assert (not (subtypep 'symbol 'keyword))) (assert (subtypep 'ratio 'real)) (assert (subtypep 'ratio 'number)) + +;;; bug 50.g: Smarten up hairy type specifiers slightly. We may wish +;;; to revisit this, perhaps by implementing a COMPLEMENT type +;;; (analogous to UNION and INTERSECTION) to take the logic out of the +;;; HAIRY domain. +(assert-nil-t (subtypep 'atom 'cons)) +(assert-nil-t (subtypep 'cons 'atom)) +(assert-nil-t (subtypep '(not list) 'cons)) +(assert-nil-t (subtypep '(not float) 'single-float)) +(assert-t-t (subtypep '(not atom) 'cons)) +(assert-t-t (subtypep 'cons '(not atom))) +;;; ANSI requires that SUBTYPEP relationships among built-in primitive +;;; types never be uncertain, i.e. never return NIL as second value. +;;; Prior to about sbcl-0.7.2.6, ATOM caused a lot of problems here +;;; (because it's a negation type, implemented as a HAIRY-TYPE, and +;;; CMU CL's HAIRY-TYPE logic punted a lot). +(assert-t-t (subtypep 'integer 'atom)) +(assert-t-t (subtypep 'function 'atom)) +(assert-nil-t (subtypep 'list 'atom)) +(assert-nil-t (subtypep 'atom 'integer)) +(assert-nil-t (subtypep 'atom 'function)) +(assert-nil-t (subtypep 'atom 'list)) +;;; ATOM is equivalent to (NOT CONS): +(assert-t-t (subtypep 'integer '(not cons))) +(assert-nil-t (subtypep 'list '(not cons))) +(assert-nil-t (subtypep '(not cons) 'integer)) +(assert-nil-t (subtypep '(not cons) 'list)) +;;; And we'd better check that all the named types are right. (We also +;;; do some more tests on ATOM here, since once CSR experimented with +;;; making it a named type.) +(assert-t-t (subtypep 'nil 'nil)) +(assert-t-t (subtypep 'nil 'atom)) +(assert-t-t (subtypep 'nil 't)) +(assert-nil-t (subtypep 'atom 'nil)) +(assert-t-t (subtypep 'atom 'atom)) +(assert-t-t (subtypep 'atom 't)) +(assert-nil-t (subtypep 't 'nil)) +(assert-nil-t (subtypep 't 'atom)) +(assert-t-t (subtypep 't 't)) +;;; Also, LIST is now somewhat special, in that (NOT LIST) should be +;;; recognized as a subtype of ATOM: +(assert-t-t (subtypep '(not list) 'atom)) +(assert-nil-t (subtypep 'atom '(not list))) +;;; These used to fail, because when the two arguments to subtypep are +;;; of different specifier-type types (e.g. HAIRY and UNION), there +;;; are two applicable type methods -- in this case +;;; HAIRY-COMPLEX-SUBTYPEP-ARG1-TYPE-METHOD and +;;; UNION-COMPLEX-SUBTYPEP-ARG2-TYPE-METHOD. Both of these exist, but +;;; [!%]INVOKE-TYPE-METHOD aren't smart enough to know that if one of +;;; them returns NIL, NIL (indicating uncertainty) it should try the +;;; other. However, as of sbcl-0.7.2.6 or so, CALL-NEXT-METHOD-ish +;;; logic in those type methods fixed it. +(assert-nil-t (subtypep '(not cons) 'list)) +(assert-nil-t (subtypep '(not single-float) 'float)) +;;; Somewhere along the line (probably when adding CALL-NEXT-METHOD-ish +;;; logic in SUBTYPEP type methods) we fixed bug 58 too: +(assert-t-t (subtypep '(and zilch integer) 'zilch)) +(assert-t-t (subtypep '(and integer zilch) 'zilch)) + +;;; Bug 84: SB-KERNEL:CSUBTYPEP was a bit enthusiastic at +;;; special-casing calls to subtypep involving *EMPTY-TYPE*, +;;; corresponding to the NIL type-specifier; we were bogusly returning +;;; NIL, T (indicating surety) for the following: +(assert-nil-nil (subtypep '(satisfies some-undefined-fun) 'nil)) + +;;; It turns out that, as of sbcl-0.7.2, we require to be able to +;;; detect this to compile src/compiler/node.lisp (and in particular, +;;; the definition of the component structure). Since it's a sensible +;;; thing to want anyway, let's test for it here: +(assert-t-t (subtypep '(or some-undefined-type (member :no-ir2-yet :dead)) + '(or some-undefined-type (member :no-ir2-yet :dead)))) +;;; BUG 158 (failure to compile loops with vector references and +;;; increments of greater than 1) was a symptom of type system +;;; uncertainty, to wit: +(assert-t-t (subtypep '(and (mod 536870911) (or (integer 0 0) (integer 2 536870912))) + '(mod 536870911))) ; aka SB-INT:INDEX. -;;;; Douglas Thomas Crosher rewrote the CMU CL type test system to allow -;;;; inline type tests for CONDITIONs and STANDARD-OBJECTs, and generally -;;;; be nicer, and Martin Atzmueller ported the patches. -;;;; They look nice but they're nontrivial enough that it's not obvious -;;;; from inspection that everything is OK. Let's make sure that things -;;;; still basically work. +;;;; Douglas Thomas Crosher rewrote the CMU CL type test system to +;;;; allow inline type tests for CONDITIONs and STANDARD-OBJECTs, and +;;;; generally be nicer, and Martin Atzmueller ported the patches. +;;;; They look nice but they're nontrivial enough that it's not +;;;; obvious from inspection that everything is OK. Let's make sure +;;;; that things still basically work. ;; structure type tests setup (defstruct structure-foo1) @@ -145,6 +241,10 @@ ;; structure type tests (assert (typep (make-structure-foo3) 'structure-foo2)) (assert (not (typep (make-structure-foo1) 'structure-foo4))) + (assert (typep (nth-value 1 + (ignore-errors (structure-foo2-x + (make-structure-foo1)))) + 'type-error)) (assert (null (ignore-errors (setf (structure-foo2-x (make-structure-foo1)) 11)))) @@ -188,12 +288,17 @@ (assert (eq (car (sb-pcl:class-direct-superclasses (sb-pcl:find-class 'simple-condition))) (sb-pcl:find-class 'condition))) - (assert (null (set-difference - (sb-pcl:class-direct-subclasses (sb-pcl:find-class - 'simple-condition)) - (mapcar #'sb-pcl:find-class - '(simple-type-error simple-error - sb-int:simple-style-warning))))) + + (let ((subclasses (mapcar #'sb-pcl:find-class + '(simple-type-error + simple-error + simple-warning + sb-int:simple-file-error + sb-int:simple-style-warning)))) + (assert (null (set-difference + (sb-pcl:class-direct-subclasses (sb-pcl:find-class + 'simple-condition)) + subclasses)))) ;; precedence lists (assert (equal (sb-pcl:class-precedence-list @@ -243,6 +348,25 @@ #.*tests-of-inline-type-tests*) (tests-of-inline-type-tests) (format t "~&/done with compiled (TESTS-OF-INLINE-TYPE-TESTS)~%") - + +;;; Redefinition of classes should alter the type hierarchy (BUG 140): +(defclass superclass () ()) +(defclass maybe-subclass () ()) +(assert-nil-t (subtypep 'maybe-subclass 'superclass)) +(defclass maybe-subclass (superclass) ()) +(assert-t-t (subtypep 'maybe-subclass 'superclass)) +(defclass maybe-subclass () ()) +(assert-nil-t (subtypep 'maybe-subclass 'superclass)) + +;;; Prior to sbcl-0.7.6.27, there was some confusion in ARRAY types +;;; specialized on some as-yet-undefined type which would cause this +;;; program to fail (bugs #123 and #165). Verify that it doesn't. +(defun foo (x) + (declare (type (vector bar) x)) + (aref x 1)) +(deftype bar () 'single-float) +(assert (eql (foo (make-array 3 :element-type 'bar :initial-element 0.0f0)) + 0.0f0)) + ;;; success (quit :unix-status 104)