FA-333 / Integer arithmetic / Member archive

Rescaling integer ticks loses precision in an intermediate step · case 03

Large counters change by several ticks after a float conversion, or fractional source units disappear before multiplication.

Member previewVariant 3 · 3 implementations · 8 checks per implementation

Case contract

For integer ticks, positive integer source_rate, and nonnegative integer target_rate, return floor(ticks * target_rate / source_rate) exactly. Invalid rates return None. Python arbitrary-size integers are part of this model.

Why this case matters

Audio, video, and instrumentation timelines are often expressed as integer ticks at different rates. Both float conversion and premature integer division can break rescaling invariants.

One recorded failure

Sample boundary fixture

This sample comes from the broken implementation of a controlled reproducer.

Boundary fixture	Actual	Expected	Outcome
large identity conversion keeps low bits	`1152921504606846976`	`1152921504606846979`	Failed

MEMBER ARCHIVE

The complete case is available to members.

This record includes three runnable implementations, regression fixtures, execution results, and source hashes.

Member access is invitation-based. Sign in with your invited account to inspect the sources.