0.8.5.29:

[sbcl.git] / doc / efficiency.sgml

diff --git a/doc/efficiency.sgml b/doc/efficiency.sgml
index 88d7d88..2f5516b 100644 (file)
--- a/doc/efficiency.sgml
+++ b/doc/efficiency.sgml
@@ -28,7 +28,7 @@ few other points to keep in mind.
 <itemizedlist>
   <listitem><para>The &CMUCL; manual doesn't seem to state it explicitly,
     but &Python; has a mental block about type inference when
-    assignment is. involved &Python; is very aggressive and clever
+    assignment is involved. &Python; is very aggressive and clever
     about inferring the types of values bound with <function>let</>,
     <function>let*</>, inline function call, and so forth. However,
     it's much more passive and dumb about inferring the types of
@@ -39,6 +39,9 @@ few other points to keep in mind.
     (This doesn't affect its ability to benefit from explicit type
     declarations involving the assigned variables, only its ability to
     get by without explicit type declarations.)</para></listitem>
+<!-- FIXME: Python dislikes assignments, but not in type
+    inference. The real problems are loop induction, closed over
+    variables and aliases. -->
   <listitem><para>Since the time the &CMUCL; manual was written,
     &CMUCL; (and thus &SBCL;) has gotten a generational garbage
     collector. This means that there are some efficiency implications