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

90%

push

github

Scan a scope's nested functions only from the function defining it (#1073)

* Scan a scope's nested functions only from the function defining it

The closure scan of #1061 also scans every function nested in a tainted
variable's scope, since such a function can run within the trace
without the body calling it. Each function so scanned repeated that
scan for every scope enclosing it, so a function defining many closures
had each closure's scan recurse into the next, as deep as the scope had
functions. On a subject with this shape the recursion overflowed a
worker thread's stack in a parallel run.

Only the function defining a scope now scans the functions nested in
it. Every function nested there is still scanned from the definer, with
the variables it can read, so nothing is lost, and the recursion is as
deep as functions are nested.

Part of #1061.

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

* Say the siblings test depends on worker-stack size

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>

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

4999 of 5665 relevant lines covered (88.24%)

0.88 hits per line