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

90%

push

github

Refuse a layer or receiver a method's caller may vary (#1268)

* Refuse a layer or receiver a method's caller may vary

A decorated method that calls a layer passed to it, or passes one through its class as a method's receiver, may first call another layer on a retrace. The engine gives the method a node per call site, so the variation shows only across its nodes, and a parameter is read as varying, as conditions already are. A receiver chosen in the method is told apart by allocation site. The caller-side check makes the bound-call conjunct of the set-up field rule redundant, so it goes.

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

* Carry a varying layer into the functions it is passed to

A block passed on to a helper, bound or through its class, varies there too, so a parameter now varies wherever a traced call passes it a varying value. A receiver passed unbound that reads the caller's own set-up field is one object per instance.

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

* Carry a varying layer out of a call, into keywords and through a starred argument

A layer a function returns, passes by a keyword only **kwargs takes, or spreads in a starred argument may still be the varying one, so each carries the variation on. The rule stays that a parameter other than the receiver varies, whatever its points-to set shows.

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

* Show an unbound receiver fixed by how it is read

A receiver's points-to set may not hold every object a caller outside the analysis passes, so neither one allocation site nor none makes it fixed.

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

* Refuse an u... (continued)

99 of 104 new or added lines in 1 file covered. (95.19%)

6909 of 7694 relevant lines covered (89.8%)

0.9 hits per line