049 two arm shapes one commitment

✓ Passing This code compiles and runs correctly.

Code

input.k

Actual

say:miss gone
t1-inline result
say:ok file-text
t2-multiline result
t3-mixed parse-error a `|` on the call's own line commits the program to that line — a later `|` arm has nothing to hang on. For several branches give each `|` its own indented line under the bare call: `call(...)\n    | ok r |> ...\n    | error e |> ...`
say:inner miss
t4-interior result
t5-partial unhandled ok

Expected output

say:miss gone
t1-inline result
say:ok file-text
t2-multiline result
t3-mixed parse-error a `|` on the call's own line commits the program to that line — a later `|` arm has nothing to hang on. For several branches give each `|` its own indented line under the bare call: `call(...)\n    | ok r |> ...\n    | error e |> ...`
say:inner miss
t4-interior result
t5-partial unhandled ok

Flows

flow ~register click a branch to expand · @labels scroll to their anchor
register (scope: "api", source: read(1) say(1))
subflow ~run-src click a branch to expand · @labels scroll to their anchor
run (br, source)
flow ~create click a branch to expand · @labels scroll to their anchor
create (id: "c", scope: "api")

Test Configuration

MUST_RUN