krino.git/internal/engine/facts.go, branch v0.0.12rule-based file sorter in Go, shows the plan before touching anything, applies only the files you choose, and can undo any run, with s-expression rules and a GTK 4 windowhttps://git.labunix.xyz/krino.git/atom?h=v0.0.122026-09-17T12:17:54Za file's name is folded once, not once per name test2026-09-17T12:17:54ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T12:17:54Zurn:sha1:b66850cc8c584cc00bcd796eb3aa238bcf87394a
Folding is the expensive half of a name test on a name with diacritics,
and every name test of every rule folded the same name again: on Polish
names it was most of the matching work. The per-file facts memoise it,
which is where one file's work belongs - the object is per file and per
goroutine, so no lock.
4000 Polish names, twelve rules with name tests: 0.33s -> 0.13s
max-read bounds what a file becomes, not only what is read2026-09-17T12:07:37ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T12:07:37Zurn:sha1:4c6fadfab5434317357ad0272ace7927d2945942
max-read gates on file size before reading, then the text was read
whole and decoded: a file that is not valid UTF-8 decodes one byte per
code point and doubles, and normalising and folding copy that again per
set of options, with GOMAXPROCS files in flight. Twelve 40 MB files
reached 3.3 GB - enough to put a laptop into the OOM killer, with no
attacker involved, just a few big .log or .csv files.
Two bounds. The decoded text is cut to max-read at a rune boundary, so
the ceiling means what a reader takes it to mean. And extraction of
files at or above 4 MiB is rationed to two at a time, since holding
several large texts at once is what multiplies the ceiling; smaller
files, which is nearly all of them, are untouched.
twelve 40 MB files: peak RSS 3294 MB -> 728 MB, wall 27s -> 46s
two thousand small files: 0.05s both ways
The wall-clock cost falls entirely on large files needing extraction,
and buys a program that finishes instead of being killed.
the module path is git.labunix.xyz/krino2026-09-17T10:54:06ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T10:54:06Zurn:sha1:1884d56b0d399e9cdb80016a9c166b0120989933
So that go install can find it. cgit serves no go-import meta tag, so
nginx answers a ?go-get=1 request for /NAME with one pointing at
https://git.labunix.xyz/NAME.git; the alternative was carrying a .git
suffix through every import line forever.
One sed over the imports, both go.mod files, and the dependency gate's
whitelist. Nothing else depends on the path. go install works from the
next tag, the first release whose go.mod carries it.
comments that explain the code, not how it was written2026-09-17T10:11:42ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T10:11:42Zurn:sha1:bddbd74e4a73e8e32bcf648efd1cac5655f6d0cd
About 340 comments cited the development process: task and plan
numbers, fix waves, rulings, reviewers, and the author in the third
person with a date. None of that exists outside the work itself, so to
a reader it pointed at nothing. Each one now states the engineering
reason it was standing in front of; where a comment was provenance and
nothing else, it is gone.
References to docs/design.md and docs/gui-design.md by section stay:
both ship with the repository. The design documents lose their
amendment diaries - CHANGELOG.md is that record - and the GUI's says
plainly that the window has gone further than the document.
Only comments changed. Every .go file was parsed and its code printed
with comments stripped, before and after: the two hashes are identical
across all 175 files.
gui: name the other copy of a duplicate, and offer to keep this one instead2026-09-17T08:15:45ZLukasz Kasprzaklukas@labunix.xyz2026-09-17T08:15:45Zurn:sha1:a2cb20851499e9c00bd3bf642680a9ce3148cae8a rule's duplicate check failure shortens the path too2026-09-14T22:33:04ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:33:04Zurn:sha1:eb31377e43fb26a6726b741978db83453fcd7bdd(matched) is unknown after an undecided rule, so a catch-all leaves an unreadable file alone2026-09-14T22:32:11ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T22:32:11Zurn:sha1:ccd6faf3d10da0669631fb3e3ba17a46b9e63a09duplicate warnings share one format2026-09-14T21:48:23ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:48:23Zurn:sha1:1bb5097986558ee7dd3aeaf8e7defefdf91ae4b6content tests are three-valued: unknown when unreadable or read in part2026-09-14T21:39:37ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T21:39:37Zurn:sha1:c09020c2fb01da24d5befbed78ce3b73b5efbe4cplan 10: a format with no text is no match, not unreadable2026-09-14T20:23:42ZLukasz Kasprzaklukas@labunix.xyz2026-09-14T20:23:42Zurn:sha1:394d117b90ffb64c87adfc8c2436b57007840c2b