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

90%

push

github

Count a layer field only set up as one layer per instance (#1263)

* Count a layer field only set up as one layer per instance

A layer read from a field that `__init__` sets in either arm of a branch,
as `self.embedding` is when it depends on a constructor argument, may be
more than one object the engine allocates, so its call was refused for
a first call on a retrace. Only `__init__` or `build` writes that field,
though, so each instance holds one layer from construction on, and each
instance traces its own function. Such a read off the receiver is now a
fixed selection when every object the receiver may be is an instance of
the method's own class. A method called unbound on another class's
object, or a field another method rebinds, is still refused.

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

* Require a bound call for a set-up field to be one layer per instance

Each instance traces its own function only when the method is called
bound to it, as `a.project(x)` is. Called through its class, as
`Embedded.project(a, x)`, the method shares one function among its
receivers, whatever their class, so a retrace may first call another
instance's layer. A set-up field now counts as one layer per instance
only when every call of the method from program code binds its
receiver, as the engine reports per call.

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>

31 of 33 new or added lines in 1 file covered. (93.94%)

6606 of 7361 relevant lines covered (89.74%)

0.9 hits per line