FAILURE MAP
← Case archive

FA-75707 / Text diff and three-way merge / Member archive

Patch reversal: an omitted count becomes an explicit zero · case 02

Reversing a single-line hunk produces a header claiming an empty range.

Member previewVariant 2 · 3 implementations · 8 checks per implementation

Case contract

Reverse one unified hunk: swap the old and new ranges in the header, keeping each range's count omitted if it was omitted and keeping any trailing header text; swap "-" and "+" on body lines; within each run of changed lines emit the (new) removed lines before the (new) added lines; a "\" marker line stays attached to the line it follows.

Why this case matters

Reverting a change applies the reversed patch, which must still be a valid, conventionally ordered hunk.

One recorded failure

Sample boundary fixture

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

Boundary fixtureActualExpectedOutcome
omitted counts stay omitted["@@ -5,0 +5,0 @@", "-y", "+x"]["@@ -5 +5 @@", "-y", "+x"]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.

Sign in to the archive ↗