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

84%

main: 84%

Pull #866

github

Pin or decline on the eager-effective dtype a NumPy argument's consumers impose

Implements the [#861 Case 1](https://github.com/ponder-lab/Hybridize-Functions-Refactoring/issues/861) design settled on the issue thread: collect, over each parameter's direct binary-op consumers, the dtype eager coercion would impose there from the partner operand's tensor typing. A singleton set diverging from the argument evidence pins the emitted spec's dtype, whose boundary cast reproduces eager's per-op coercion; a plural set declines with HAS_CONFLICTING_EAGER_DTYPE_COERCIONS (code 22), since parallel consumptions under different dtypes admit no single signature. A ⊤ partner leaves the parameter indeterminate, firing neither. The compute must precede the static-shape-read check in the processor: that check materializes the memoized signature, and a later-computed pin would miss the emitted spec.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AM8pvSeP5UqDyyTn9h5E2P

88 of 95 new or added lines in 4 files covered. (92.63%)

3139 of 3746 relevant lines covered (83.8%)

0.84 hits per line