Repository navigation
Release 0.0.7: centralize benchmark behavior in Rust - #8
Merged
Merged
Conversation
added 14 commits
November 2, 2026 20:34
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Benchmark rules were independently implemented in the Rust, Python and Swift interfaces. This release moves aggregation, suite execution and stopping, argument validation, the benchmark catalog, defaults and calibration into the Rust core. Python and Swift call the C ABI and retain responsibility for host types, callbacks, signals and handle ownership.
The Python metadata snapshot is generated from Rust, so imports, calibration inspection and CLI help remain available without loading the native library. Native loading now precedes benchmark range validation, including CLI failure reporting. Numeric validation quietly rejects NaN/infinity; non-string unknown-name diagnostics raise TypeError. The documented public API and host comparison/conversion behavior are covered by regression tests.
The change also fixes native-loader and callback ownership, cancellation and repeated-signal cleanup, concurrent artifact publication, interrupted/forked publication lock ownership, installer copy policies and PyPy compatibility. Version 0.0.7 is synchronized across Python, Cargo and documented dependency pins.
While streaming intermediate results, the CLI blocks SIGINT in its parked observer so a process-directed interrupt reaches blocked main-thread output. The worker restores its exact previous signal mask after acknowledgement and after publication, wait or clear failures.
Explicit compatibility decisions are documented: Python retains host comparisons and converts each requested success value to bool once; CLI internal thread context inheritance is unspecified; native numeric and duration validation classifies stored values independently of FPU flushing. The final contract tests kill 10 directed mutants.
CI fixture corrections preserve strict behavioral checks while accepting legitimate scheduling outcomes: first-child no-work is retried only before the targeted conversion; stream policy is inspected at the actual first callback without assuming warmup; FPU measurements exclude automatic GC statistics. The three fixture families kill 18 directed mutants, with 2734 local Python tests passing.
Off-main CLI tests directly observe signal-handler ownership and accept only successful output or the exact documented no-work failure; nanosecond controls pin that boundary. Eight directed mutations cover signal setup/restoration, diagnostics, exit status, progress phase and final fraction.
Validation:
tests/core-centralization-plan.mdand the task's local audit reports.Publication uses the existing release workflow after merge: five native wheel targets, sdist, crates.io, C/native archives and universal Swift/XCFramework assets. No release tags are created manually.