Fixup discussion of OPTIMIZE/DYNAMIC-EXTENT declarations as
suggested by APD on sbcl-devel
(length rest))
@end lisp
-because the @code{optimize} declaration affects the binding, not the
-allocation.
+because both the allocation of the @code{&rest} list and the variable
+binding are outside the scope of the @code{optimize} declaration.
There are many cases when dynamic-extent declarations could be useful.
At present, SBCL implements
;;; checkins which aren't released. (And occasionally for internal
;;; versions, especially for internal versions off the main CVS
;;; branch, it gets hairier, e.g. "0.pre7.14.flaky4.13".)
-"0.8.9.20"
+"0.8.9.21"