✓
Passing Passing: the compiler rejects this program as expected.
Code
// Test: Void event chaining with nested continuations
// When chaining void -> event with branches, should parse nested continuations correctly
// Pattern: void-event() |> branching-event()
// | branch1 |> _
// | branch2 |> _
~tor void-event {}
~tor branching-event {}
// MUST_ERROR: branching-event is declared void (no branches), so `| error` is a
// branch handler on an event that has no branches — category error.
~void-event() |> branching-event()
| error |> _
Actual compiler output
error[KORU021]: event 'input:branching-event' has no branch 'error' (available: (none))
--> tests/regression/200_COMPILER_FEATURES/210_PARSER/210_014_void_chaining_nested/input.kz:14:0
❌ Compiler coordination error: Incomplete branch coverage
(set KORU_BACKEND_TRACE=1 for the backend return trace)Must fail at runtime:
Program must error when executed.
Expected patterns
Each line is a regex that must match the compiler error output.
# Test 210_014: Branch handler attached to void event
#
# `branching-event` is declared with no branches (void event). The flow
# attaches `| error |>` — a branch handler for a branch the event does
# not produce. The compiler should reject this with a clear
# coverage/category error that names the event and indicates the
# branch is not declared.
#
# Currently emits: KORU021 "event 'input:branching-event' has no
# branch 'error' (available: (none))". Pin matches current behavior.
error\[KORU\d+\]
branching-event
no branch
input\.kzFlows
flow ~void-event click a branch to expand · @labels scroll to their anchor
void-event
Test Configuration
MUST_ERROR