✗
Failing This test is currently failing.
Failed: frontend
Failure Output
Showing last 10 of 33 lines
error[KORU010]: '|>' cannot start a line
--> tests/regression/300_ADVANCED_FEATURES/310_COMPTIME/310_013_tap_chains/input.kz:20:0
|
20 | |> _
| ^^
hint: '|>' is inline glue, never a line start — it joins a branch handler to its body and chains steps on one line.
• Keep the chain inline regardless of length.
• If a step ends in a multi-line { } block, put the next |> on the same line as that block's closing } : pairwise { ... } |> self { ... }
• Void chains may instead split into separate top-level statements (~A() then ~B()).
• Drop a trailing |> _ if the head already suffices.Code
// Test tap chains - tap invokes event that also has taps
// This verifies TAP_FUNCTION_CONTEXT prevents infinite recursion
const std = @import("std");
~import std/taps
~event main-flow {}
~event logger {}
|> logger()
|> _
// Question: Should this tap on logger fire when logger is invoked from a tap?
// Answer: YES - chained taps fire by default (full observability)
// Use [opaque] annotation if you need to hide internal implementation from tap matching
~tap(logger -> *)
|> metrics()
|> _
~main-flow()
|> _Expected output
Main flow executed
Logger invoked
Metrics collected
Test Configuration
MUST_RUN