Review the RowFn prototype, merge develop, and apply the review findings - #9245
Conversation
2cfa807 to
c139786
Compare
Merging this PR will regress 42 benchmarks
Warning Please fix the performance issues or acknowledge them on CodSpeed. Performance Changes
Tip Investigate this regression by commenting Comparing Footnotes
|
Cleanup, corrected documentation, and test coverage from a review of the RowFn API, its execution logic, and the scalar function implementations. The author-facing API is unchanged and every visit_prepared_into monomorph emits identical IR to the pre-review commit. Signed-off-by: Connor Tsui <connor@spiraldb.com>
c139786 to
75c4707
Compare
Progress towards #9128. Cleanup from a review of the
RowFnAPI, the execution logic, and the scalar function implementations: deletes theInputElement::decode_null_tolerantoverrides that only restated the default, sharesresolve_validitybetweenexecute_filteredand the forced-strategy test seam, corrects the dense-retry comment, de-duplicatesl2_norm_rowintovortex-tensor/src/utils.rs, drops the now-callerlessmap_checked_into, and pinsgeoto=0.31.0becausecontains_routetranscribes itsimpl_contains_from_relate!dispatch table and a patch can reshuffle that with no API change. The author-facing API is unchanged: every proposal that would have altered it was backed out, andSCALAR_FN_HANDOFF.mdrecords which ones and why.The checked-arithmetic macro collapse this review also found is #9248 against
developinstead, sincedevelopcarries the same duplication.Checks
The optimized IR of every
visit_prepared_intomonomorph is unchanged from the pre-review commit. Runtime benchmarks were not usable as a gate on this host, where repeated pinned runs of the same binary disagreed by up to 4x.