ponder-lab / Hybridize-Functions-Refactoring / #3444

88%

main: 90%

push

github

Pass a scanned function only the closure variables it can read (#1070)

* Pass a scanned function only the closure variables it can read

The closure taint of #1061 handed every function it scanned all the
tainted lexical variables in view, including ones from scopes that do
not enclose the function, such as a top-level helper that a closure
calls. Such a function cannot read those variables, but scanning it
with them made it rescan every closure nested in their scopes, and
sibling closures then rescanned one another under ever-growing seeds,
each a new memo key. On a subject whose function has many sibling
lambdas, each calling its own helper, the scan overflowed the stack.

A scanned function now receives only the variables whose defining scope
encloses it. A closure called from outside its scope is still scanned
from the scope's own node, so nothing it can read is lost.

Part of #1061.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NTnpjPjJj2aZy1ZkUD1eAn

* Say why filtering the closure seeds preserves results

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01NTnpjPjJj2aZy1ZkUD1eAn

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>

24 of 24 new or added lines in 2 files covered. (100.0%)

4998 of 5664 relevant lines covered (88.24%)

0.88 hits per line