FA-96038 / Postal address normalization / Member archive

House number parser: improper fractions are consumed · case 03

"13 2/2 FAKE ST" consumes "2/2" as a fraction.

Member previewVariant 3 · 3 implementations · 12 checks per implementation

Case contract

Uppercase and split the line. The first token must start with digits: the digits form the house number (an int, which must not be 0); an optional single hyphen is dropped and at most one letter may follow as the suffix. If the second token is a/b with b in 2,3,4 and 0 < a < b it is the fraction and is consumed. Return [number, suffix, fraction, rest] or None.

Why this case matters

House-number parsing decides the delivery point; fractions and suffixes distinguish separate dwellings on one lot.

One recorded failure

Sample boundary fixture

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

Boundary fixture	Actual	Expected	Outcome
improper fraction stays in the street	`[33, "", "2/2", "FAKE ST"]`	`[33, "", "", "2/2 FAKE ST"]`	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.