It doesn't matter too much, but putting the logic for let and mv-let
where the other local call logic is makes it clearer that these
propagate constraints from local call arguments to
variables. Otherwise we were bending backwards a bit to find the call
node just to do that. Whereas the bind node is not something we care
about at all, and could not generalize to e.g. ASSIGNMENT or the other
functional kinds.
It also makes it obvious that we don't handle mv-combinations.
GENERAL INFORMATION
Welcome to SBCL.
If you'd like to install or build the system, see the "INSTALL" file.
To find out more about who created the system, see the "CREDITS" file.
If you'd like information about the legalities of copying the system,
see the "COPYING" file.
The "DOCUMENTATION" file describes the various formats and ways to
access the documentation.
The system is a work in progress. See the "TODO" file in the source
distribution for some highlights.
See the "BUGS" file for how to view or report bugs.
If you'd like to make suggestions or help to improve the system,
please send mail to one of the mailing lists:
sbcl-help@lists.sourceforge.net
sbcl-devel@lists.sourceforge.net
Note that as a spam reduction measure you must subscribe to the lists
before you can post: https://sourceforge.net/p/sbcl/mailman/
The "HACKING" file has more details regarding hacking on and
contributing to SBCL.
SYSTEM-SPECIFIC HINTS
for OpenBSD 6.0 and newer:
SBCL must be built and run from a filesystem with the "wxallowed"
mount option, such as /usr/local in the default install.
1ac5b145ea