✗
Failing This test is currently failing.
Failed: backend-exec
Error Details
output_emitted.zig:12:75: error: use of undeclared identifier 'string'
Failure Output
🎯 Compiler coordination: Passes: 14 (flow-based: frontend, analysis, emission)
Error: output_emitted.zig:12:75: error: use of undeclared identifier 'string'
const result_0 = koru_std.koru_map.new_event.handler(.{ .string = string, .i64 = i64 });
^~~~~~Code
// PINNED GAP (currently RED) — the IDEAL unified generic-map surface we want
// after the naive phase: ONE `std/map` whose key/value types are chosen at
// construction, with ops that dispatch on the handle's concrete type. Today this
// fails: `new(string, i64)` is not a [transform], and a string-typed `set`/`get`
// in the `map` module collides with the i64 ones ("duplicate struct member
// name") because events lower to a `<name>_event` member keyed by NAME ONLY —
// there is no overload-by-handle-type and no type registry for the call site to
// resolve against. This is THE dispatch gap the naive per-type modules
// (std/string-map) route around honestly; greening this test is the post-AoC
// generics milestone (ties to the type-registry work).
import std/io
import std/map
std/map:new(string, i64)
| map m |> std/map:set(m, k: "a", v: 1) |> std/map:get(m, k: "a")
| value v |> std/io:print.ln("{{ v:d }}") |> std/map:free(m)
| missing |> std/io:print.ln("MISSING") |> std/map:free(m)
| err e |> std/io:print.ln("ERR {{ e:s }}")
Expected output
1
Flows
flow ~new click a branch to expand · @labels scroll to their anchor
new (string, i64)
Test Configuration
MUST_RUN