[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
**DRAFT** issue COMPILE-ENVIRONMENT-CONSISTENCY
- To: email@example.com
- Subject: **DRAFT** issue COMPILE-ENVIRONMENT-CONSISTENCY
- From: Eric Benson <firstname.lastname@example.org>
- Date: Fri, 23 Sep 88 17:38:11 pdt
- Cc: email@example.com
- In-reply-to: Sandra J Loosemore's message of Fri, 23 Sep 88 11:56:22 MDT <8809231756.AA02532@defun.utah.edu>
[CC'ed to cl-compiler instead of x3j13.]
Do you want to allow the compiler to make assumptions based on FTYPE
proclamations or declarations, even if the function whose type is
being declared is not declared INLINE, not a built-in Common Lisp
function, and not defined in the same file as the call to the
function? I think this is sensible and it reflects current practice.
You could add another condition in section (2), e.g.
(i) The compiler may assume that the signature (or "contract") of
functions with FTYPE information available will not change.
This should really go between (d) and (e) instead of after (h).