| blob | 4f1bec233634d3112f529a42e0983adb93127213 |
1 ;;;; This software is part of the SBCL system. See the README file for
2 ;;;; more information.
3 ;;;;
4 ;;;; This software is derived from the CMU CL system, which was
5 ;;;; written at Carnegie Mellon University and released into the
6 ;;;; public domain. The software is in the public domain and is
7 ;;;; provided with absolutely no warranty. See the COPYING and CREDITS
8 ;;;; files for more information.
12 ;;; (Note that when cross-compiling, SB!XC:TYPEP is interpreted as a
13 ;;; test that the host Lisp object OBJECT translates to a target SBCL
14 ;;; type TYPE. This behavior is needed e.g. to test for the validity
15 ;;; of numeric subtype bounds read when cross-compiling.)
17 "Is OBJECT of type TYPE?"
20 ;; Actually interpreting types at runtime is done by %TYPEP. The
21 ;; cost of the extra function call here should be negligible
22 ;; compared to the cost of interpreting types. (And the compiler
23 ;; tries hard to optimize away the interpretation of types at
24 ;; runtime, and when it succeeds, we never get here anyway.)
27 ;;; the actual TYPEP engine. The compiler only generates calls to this
28 ;;; function when it can't figure out anything more intelligent to do.
30 ;; Checking CTYPE-P on the specifier, as used to be done, is not right.
31 ;; If the specifier were a CTYPE we shouldn't have gotten here.
48 ;; two components of a COMPLEX are always coerced to
49 ;; be the same, e.g. (COMPLEX 1.0 3/2) => #C(1.0 1.5).
50 ;; Dunno why that holds, though -- ANSI? Python
51 ;; tradition? marsh faerie spirits? -- WHN 2001-10-27
54 object)))
77 (:complex
81 (:real
103 ;; FIXME: treatment of compound types involving unknown types
104 ;; is generally bogus throughout the system, e.g.
105 ;; (TYPEP MY-ARRAY '(ARRAY (OR BAD1 BAD2) *)) => T
106 ;; because (OR BAD1 BAD2) is not represented as an UNKNOWN-TYPE,
107 ;; and has specialized type '*.
108 ;; One way to fix this is that every CTYPE needs a bit to indicate
109 ;; whether any subpart of it is unknown, or else when parsing,
110 ;; we should always return an UNKNOWN if any subpart is unknown,
111 ;; or else any time we use a CTYPE, we do a deep traversal
112 ;; to detect embedded UNKNOWNs (which seems bad for performance).
114 ;; better to fail this way than to get bogosities like
115 ;; (TYPEP (MAKE-ARRAY 11) '(ARRAY SOME-UNDEFINED-TYPE)) => T
118 t)
121 ;; FIXME: not the most efficient.
123 object)))))))
126 t))
129 ;; It might be more efficient to check that OBJECT is either INSTANCEP
130 ;; or FUNCALLABLE-INSTANCE-P before making this call.
131 ;; But doing that would change the behavior if %%TYPEP were ever called
132 ;; with a built-in classoid whose members are not instances.
133 ;; e.g. (%%typep (find-fdefn 'car) (specifier-type 'fdefn))
134 ;; I'm not sure if that can happen.
147 #!+sb-simd-pack
162 ;; dunno how to do this ANSIly -- WHN 19990413
164 ;; Parse it again to make sure it's really undefined.
173 ;; Now the tricky stuff.
180 ;; Note: it should be safe to skip OR here, because union
181 ;; types can always be represented as UNION-TYPE in general
182 ;; or other CTYPEs in special cases; we never need to use
183 ;; HAIRY-TYPE for them.
204 type
208 ;; Most of the time an undefined type becomes defined is
209 ;; through structure or class definition, optimize that case
213 ;; TODO: structures can be optimized even further
222 object)))
230 ;;; Do a type test from a class cell, allowing forward reference and
231 ;;; redefinition.
243 ;;; Test whether OBJ-LAYOUT is from an instance of CLASSOID.
245 ;; FIXME & KLUDGE: We could like to grab the *WORLD-LOCK* here (to ensure that
246 ;; class graph doesn't change while we're doing the typep test), but in
247 ;; practice that causes trouble -- deadlocking against the compiler
248 ;; if compiler output (or macro, or compiler-macro expansion) causes
249 ;; another thread to do stuff. Not locking is a shoddy bandaid as it is remains
250 ;; easy to trigger the same problem using a different code path -- but in practice
251 ;; locking here makes Slime unusable with :SPAWN in post *WORLD-LOCK* world. So...
252 ;; -- NS 2008-12-16