✓
Passing This code compiles and runs correctly.
Code
// ============================================================================
// Test 210_081: FRONTEND_COMPILE_ERROR — bare `|? |> _` refuses at parse.
//
// There is no catch-all spelling, in any form. Unhandled `?` branches
// need no marker: the producer's `?` already says they may go unnamed,
// and "unnamed" is absence — not a case a consumer may write an arm for.
//
// 210_011/210_017 pin the metatype-bound refusal; this file pins the
// barest form.
// ============================================================================
~tor process { value: u32 }
| success u32
| ?warning string
| ?debug string
~proc process|zig {
return .{ .success = value * 2 };
}
~process(value: 10)
| success _ |> _
|? |> _
Must fail at frontend compile:
Parsing or type-checking must reject the program.
Expected patterns
Each line is a regex that must match the program output.
error\[PARSE003\]
catch-all continuations are not a thing
\|\? \|> _