1:22:00no-defun-allowedOne of the outputs is called and the output of that is AREFed to lookup a function in the global environment, so it appears different.
1:23:16no-defun-allowedNo, not called, but there's an AREF and CAR.
1:28:46Bikeoh, well, the first argument is the static environment, aka the closure vector
7:07:08no-defun-allowedOkay, I think how I get how the static environment (with the HIR evaluator) works now. Just to check: if it's a top level enter, then the first 5 (sicl-compiler:+first-constant-index+) values in the static environment are installed by the host with some common functions, and the function cells corresponding to the function-names are installed after those. Otherwise, the initialize-closure instruction copies in the
7:07:08no-defun-allowedfirst 5 values from the caller, and takes the rest of the values in the static environment as inputs?