[Ecls-list] Type propagator and "bogus" existing code

[dherring at tentpost.com]

> Anyway, I think I will settle for a simple style warning. The disadvantage
> is that this will mask real problems, such as real type errors, but given
> Common Lisp's semantics and the code out there, nothing else seems
> sensible.

+1

Since such warnings are not part of the standard, users should not be
required to address them simply to get code to compile (especially in
cases where macros may generate stray code).  However, such warnings may
be useful, and compiler notes are not as easily handled automatically.

- Daniel