Overview
| Comment: | 0.3.3: version bump and release notes |
|---|---|
| Timelines: | family | ancestors | descendants | both | trunk | version-0.3.3 |
| Files: | files | file ages | folders |
| SHA3-256: |
441d99370fe66414f2f09e91a8ac7d58 |
| User & Date: | dmestas on 2026-09-02 02:57:23.381 |
| Other Links: | manifest | tags |
Context
|
2026-09-02
| ||
| 22:15 | zit#173: route ordering tiebreaks through the hashOf door; trap the raw store under image backing check-in: 8216f43a66 user: dmestas tags: trunk | |
| 02:57 | 0.3.3: version bump and release notes check-in: 441d99370f user: dmestas tags: trunk, version-0.3.3 | |
| 01:32 |
annotate walks the file's versions, not the whole ancestry
Every ancestor cost a manifest read and a full-file line diff — ~36k of each on SQLite where ~400 touched the file. The cache records already say who changed PATH (their diff is against the primary parent, so unlisted means byte-equal there): untouched ancestors inherit the parent's content pointer, the engine copies the parent's origins on pointer-identity, and the LCS trims the common prefix/suffix before its O(n*m) table. Unfinishable on SQLite before; 0.5-1.2s typical, 57s for a 15k-line heavily-edited file (the multi-hunk quadratic middle remains — a real diff core is the named follow-up). Attribution of a repeated line between equally-valid origins can shift, as any LCS tiebreak may. zit#172 check-in: 22bdf84fd3 user: dmestas tags: trunk | |
Changes
Modified build.zig.zon
from [2cb8b1cc53]
to [e069ec68d4].
[diff]
Added docs/RELEASE-NOTES-0.3.3.md version [0b464491b3].
Modified src/main.zig
from [aa706cccd6]
to [5fa67f37b8].
[diff]