X-Git-Url: http://repo.macrolet.net/gitweb/?a=blobdiff_plain;f=doc%2Fefficiency.sgml;h=2f5516ba4c0909a2d8b853502a86129447c9014f;hb=4ed3f0d08c3a57a6762018d9622f253ab9d0f2b6;hp=88d7d88b83ff50dfaf39ff2b68a797e7a38c56a0;hpb=a530bbe337109d898d5b4a001fc8f1afa3b5dc39;p=sbcl.git diff --git a/doc/efficiency.sgml b/doc/efficiency.sgml index 88d7d88..2f5516b 100644 --- a/doc/efficiency.sgml +++ b/doc/efficiency.sgml @@ -28,7 +28,7 @@ few other points to keep in mind. 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 let, 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.) + 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