Stefan Haller 185f147db2 Number the lines of a patch in one pass when indexing its change lines ...

Several actions on the selected lines of a diff look up those lines in
the diff of their file by their line numbers: staging, unstaging and
discarding them, editing the hunk they are in, and adding them to a
custom patch. Showing which lines of a diff are in the custom patch
does the same lookup the other way round. For this, the change lines of
the file's diff are indexed by their line numbers.

The index asked the patch for the number of each change line separately,
and each of these calls counts the lines of the hunk before the line. So
for a new file of 100,000 lines, building the index took 2 seconds.
Number all lines of the patch in one pass instead. Building the index
for that file now takes 4 milliseconds.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

2026-10-14 08:41:50 +02:00

..

format.go

Export PatchLine.isChange

2025-07-04 10:14:35 +02:00

hunk.go

Add a well-formedness check for a parsed patch

2026-10-04 19:01:01 +02:00

parse.go

Add a well-formedness check for a parsed patch

2026-10-04 19:01:01 +02:00

patch_builder_test.go

Preserve whole-file operations for added and deleted files

2026-10-05 11:44:42 +02:00

patch_builder.go

Number the lines of a patch in one pass when indexing its change lines

2026-10-14 08:41:50 +02:00

patch_line.go

Fix selection after staging an added line

2026-03-19 16:57:53 +01:00

patch_test.go

Number the lines of a diff in one pass when parsing it

2026-10-14 08:41:50 +02:00

patch.go

Number the lines of a diff in one pass when parsing it

2026-10-14 08:41:50 +02:00

transform.go

Show renamed files in the custom patch builder

2026-07-04 13:05:09 +02:00