fix constant-list-related initargs in CTOR optimization
authorChristophe Rhodes <csr21@cantab.net>
Wed, 16 Jan 2013 13:51:19 +0000 (13:51 +0000)
committerChristophe Rhodes <csr21@cantab.net>
Fri, 18 Jan 2013 22:51:23 +0000 (22:51 +0000)
commit3eed77547e03a57c9be57db74081ee0f39ed0fa6
treeb1bc0c24e3dfa7232aac588f3ddac15da30f2cfa
parent63e78fc74df6e60019a9952531c4b7608656f07e
fix constant-list-related initargs in CTOR optimization

lp#1099708, reported by Derek Baldwin; also test for _3b's #sbcl irc insight
that this would break non-EQLity of distinct but EQUAL list constants

Also deal with pathnames, bit-vectors and strings, which are precisely the
types EQUAL descends into.

(The general problem of function names being looked up using EQUAL remains
a problem, though with fewer observable consequences: for example, methods
with EQUAL eql-specializers will have their function names collide with
each other, though since in CLOS the functions are looked up through the
method objects this is less serious than with CTORs.
NEWS
src/pcl/ctor.lisp
tests/clos.impure.lisp