010 vendor patch survives sync

✓ Passing This code compiles and runs correctly.

Code

// Pins the whole point of vendoring: a tree you PATCHED on purpose compiles, and
// the record of what you copied survives the command that accepts the patch.
//
// The lock here was produced by running `vendor sync` over a patched tree, so the
// file itself is the evidence — `as-copied` and `origin` are still present after
// the write that moved `as-compiled`. Before the split, accepting your own fix
// destroyed the only record of what it was a fix TO.
//
// The patch changes the greeting, so the expected output proves the patched
// library is what actually ran — not merely that a patched tree was tolerated.

import std/io
import std/vendor

std/vendor:bindings {
    koru/vaxis: ./vendored/vaxis
}

import koru/vaxis

koru/vaxis:greet(): v |> std/io:print.ln("{{ v:s }}")

input.k

Actual

PATCHED vaxis

Expected output

PATCHED vaxis

Flows

flow ~bindings click a branch to expand · @labels scroll to their anchor

bindings (source: koru/vaxis: ./vendored/vaxis)

flow ~greet click a branch to expand · @labels scroll to their anchor

greet

Imported Files

~pub tor greet {} -> string

~proc greet|zig {
    // MY PATCH: upstream's greeting was wrong for our locale.
    return "PATCHED vaxis";
}

vendored/vaxis/index.kz

Test Configuration

MUST_RUN

← 009 vendor lock v1 still pins 011 vendor gate is the compiled tree →