Zig on tsvinc

The engine got credit for the quant

Fri, 16 Oct 2026 00:00:00 +0000

Assumes you've served a GGUF through llama.cpp and know what a quant is.

Two inference engines ran the same 17-gigabyte GGUF through the same nine Zig agent runs, and each finished with 7 PASS, 1 PARTIAL, 1 FAIL. A tie is a boring result. This one was the most useful number of the week, because the evening before, one of those engines had been beating the other 7 to 3.

Zig needed context, not time

Thu, 15 Oct 2026 00:00:00 +0000

Assumes you've driven a coding agent against a local llama.cpp server and know what context compaction is.

When an agent run dies at the wall clock, the obvious diagnosis is that it was slow, and the obvious fix is a longer wall. Four 27B models on a Zig task were hitting a one-hour limit in about half their runs at 64k context, so twelve runs of the test-first prompt got four hours instead.

The deadlock test can't see a half-held lock

Tue, 13 Oct 2026 00:00:00 +0000

Assumes you have written a two-account transfer under per-account locks, and know what a mutation test is.

At 128k context and a four-hour budget, four 27B local models ran a Zig ledger task 36 times through OpenCode. All 36 passed all 15 hidden core tests. All 36 had written their own concurrency test with real threads, because the prompt asked for one.

Then the scorer removed the second account lock from each transfer and ran everything again. The hidden suite failed on every mutant it could score. The models' own suites failed in 4 of 11 scoreable spec runs, 0 of 9 clean review runs, and 6 of 9 test-first runs.

I blamed OpenCode; a 2-bit model passed Zig in it

Mon, 12 Oct 2026 00:00:00 +0000

Assumes you've driven a coding agent against a local llama.cpp server and know what MoE and a Q2 quant are.

OpenCode has two features that look bad in a Zig agent run at 64k context.

The first is auto-compaction. When the conversation fills the window, OpenCode summarizes it and carries on from the summary. OpenCode's config docs describe the default as compacting "when context is full". On a Zig task, that window fills with compiler errors, test files and stress-test output, and a summary can only keep so much of it.

Zig's defer ends at the closing brace

Mon, 12 Oct 2026 00:00:00 +0000

Assumes you have guarded a critical section with a mutex and defer unlock in Go.

Moving money between two accounts under per-account locks has one famous trap, and it is the order. Lock A then B in one thread, B then A in another, and the two transfers deadlock. The textbook answer is to sort the IDs and always lock the lower one first. It is in every concurrency chapter.