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

89%

main: 90%

push

github

Record a decorator whose name can't be resolved (#1142)

* Record a decorator whose name can't be resolved

When a decorator's name lookup fails, the function now carries an
`UNRESOLVED_DECORATOR` warning naming the decorator and the exception
kind, instead of the decorator being dropped with only a log line. The
hybridization check and the decorator naming both record it, once per
decorator. The evaluator prints decorators before statuses so that an
entry recorded while naming them reaches `statuses.csv`.

Part of #1121.

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

* Resolve decorator names before any per-function CSV

The evaluator now names every function's decorators before it writes
`functions.csv`, so its severity column and `statuses.csv` see the same
entries. The assertions in the transformations look names up without
recording, so enabling assertions doesn't change the entries, and the
`tf.custom_gradient` lookups record an unresolved decorator through the
same once-per-decorator path.

Part of #1121.

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

* Test the unresolved decorator in the custom_gradient lookups

Beneath `@tf.function`, a decorator whose name can't be resolved counts
as intervening; on a method, it isn't taken for `tf.custom_gradient`.
The reasons named in the entry are now a table keyed by the exception
rather than a chain of type tests.

Part of #1121.

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>

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

5406 of 6079 relevant lines covered (88.93%)

0.89 hits per line