FA-6569 / Calendar arithmetic / Member archive

Seconds since midnight · case 04

Decimal clock encoding is confused with elapsed seconds.

Member previewVariant 4 · 3 implementations · 4 checks per implementation

Case contract

Valid ISO Gregorian dates in years 1 through 9999; generated dates must remain in that range. Month is 1 through 12 and zero-based weekday is Monday 0 through Sunday 6 unless the output convention says otherwise. hour=0..23, minute=0..59 and second=0..59; leap seconds are outside this model. Exact operational definition: hour*3600+minute*60+second

Why this case matters

Small exact fixtures expose this error without platform timing, external services, or probabilistic observations. Calendar conventions results depend on the stated convention.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
fixture 1: (1, 2, 3)	`10203`	`3723`	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.