- Aug 01, 1992
-
-
ram authored
conversion is done, since this violates stack discipline. All type checks are done on the fly during byte conversion.
-
- Jul 21, 1992
-
-
ram authored
This lets type checking assume that the continuation does have a DEST, and also avoids some unnecessary work.
-
- Mar 21, 1992
-
-
wlott authored
-
- Mar 18, 1991
-
-
ram authored
(for testing its effectiveness.)
-
- Feb 20, 1991
-
-
ram authored
-
- Dec 28, 1990
-
-
ram authored
debug-info is not important, so that we can use CHECK-STRUCTURE, etc. Changed TYPE-TEST-COST to penalize predicates as opposed to check templates so that we will use a check template in favor of a "same cost" predicate.
-
- Nov 13, 1990
-
-
wlott authored
from the correct backend for runtime.
-
- Oct 17, 1990
-
-
ram authored
tweaked output format a bit.
-
- Oct 11, 1990
-
-
ram authored
unknown values even though they are really fixed-values (and people might be depending on the check, like non-local RETURN-FROM.) Don't do an inline type check for the argument of a full call, even when we are "sure" that there is an error, since the user might want to fix the problem by redefining the callee, and not by changing the caller (or callers.) Spiffed up type error warnings to use the variable we are binding to as context when doing a local call. Also, instead of saying we "got NIL", we say we got an expression that didn't return. Changed type error checking to consistently flame about all losing uses of a continuation, instead of maybe only flaming about the first one, or even totally missing it if the first use we see is non-erroneous but hairy. Also, don't do type warnings on continuations with :DELETE TYPE-CHECK, since those are the result of hairy type checks.
-
- Sep 05, 1990
-
-
ram authored
the continuation is incorrect, instead of only warning when the first use happened to be incorrect.
-
- Jul 23, 1990
-
-
ram authored
-
- Jun 06, 1990
-
-
ram authored
types from being checked, even when they are buried in other types (like OR.)
-
- Jun 01, 1990
-
-
ram authored
confused by complex function types.
-
- May 30, 1990
-
-
cvs2git authored
-
- May 22, 1990
- May 21, 1990
-
-
ram authored
VALID-FUNCTION-USE is unable to determine the whether the template applies. If the VOP operand is unrestrictive, but we know it is of an unknown type, then the type-operation will fail but the template can still be selected, since PRIMITIVE-TYPE isn't fooled.
-
- May 17, 1990
-
-
ram authored
(i.e. COMMON). Also, we don't preserve the original check just because there was some supertype predicate.
-
- May 16, 1990
-
-
ram authored
-
- May 12, 1990
-
-
ram authored
be totally flushed only when safety = 0. Also, when printing a type warning, check to see if the losing value is a constant, and if so, print it instead of its type.
-
- Mar 27, 1990
-
-
ram authored
a type error.
-
- Mar 05, 1990
-
-
cvs2git authored
-
- Feb 06, 1990
-
-
wlott authored
-