109 command gated import absent

✓ Passing This code compiles and runs correctly.

Code

// The negative twin of 310_108: `command(trace)` with NO command in the
// invocation resolves absent → false, the import is excluded (loudly, on
// stderr — the gate's resolution report), and the program compiles and runs
// WITHOUT the module. No tap line: exclusion is the pinned behavior.

const std = @import("std");

~[command(trace)]import app/test_lib/tracer

~tor compute { x: i32 } -> i32

~proc compute|zig {
    std.debug.print("compute({d})\n", .{x});
    return x * 2;
}

~tor display { value: i32 }

~proc display|zig {
    std.debug.print("Final: {d}\n", .{value});
}

~compute(x: 21): r |> display(value: r)

input.kz

Actual

compute(21)
Final: 42

Expected output

compute(21)
Final: 42

Flows

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

compute (x: 21)

Imported Files

// Tap module — importing it is what wires the tap (the 310_001 mechanism).
// The pin's gated import makes that wiring conditional: this module's output
// appears exactly when the import survives the annotation gate.

const std = @import("std");
~import std/taps

~pub tor log { event_name: string }

~proc log|zig {
    std.debug.print("[TAP] {s}\n", .{event_name});
}

// compute is a bare-return `-> T` event, so the tap binds the produced value
// with `: r` (call-site bind rule, Lars-ruled 2026-06-25; 310_001 is the green
// precedent) — a branch tap has no named branch to match on a bare return.
~tap(input:compute -> input:display): r |> log(event_name: "compute")

test_lib/tracer.kz

Test Configuration

MUST_RUN

← 108 command gated import 110 glance command →