Skip to content
Snippets Groups Projects
Commit d24f0501 authored by ram's avatar ram
Browse files

Force type check conversion of continuations that may be forced to

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.
parent a15164d7
No related branches found
No related tags found
No related merge requests found
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment