064 reject phantom primitive mismatch

✓ Passing Passing: the compiler rejects this program as expected.

Code

// Test (negative): passing a bare `f32` (no phantom label) where `f32[celsius]`
// is required must be rejected by the phantom semantic checker.
//
// Safety counterpart to 330_063_phantom_state_on_primitive — that test proves
// matching phantoms compile and a conversion event transitions across labels;
// this one proves that an un-labelled f32 can't masquerade as a labelled one.

~tor read-raw { sensor_id: u8 } -> f32                          // BARE f32 — no phantom label

~read-raw -> 22.5

~tor to-fahrenheit { c: f32<celsius> }   // requires [celsius] -> f32<fahrenheit>

~to-fahrenheit -> c * 9.0 / 5.0 + 32.0

~read-raw(sensor_id: 1): t |> to-fahrenheit(c: t): _     // ERROR: f32 cannot satisfy f32[celsius]

input.kz

Actual compiler output

error[KORU030]: Phantom state mismatch: argument 'c' has no tracked phantom state, but this event requires state '<celsius>'.
  --> tests/regression/300_ADVANCED_FEATURES/330_PHANTOM_TYPES/330_064_reject_phantom_primitive_mismatch/input.kz:16:0

❌ Compiler coordination error: Phantom semantic validation failed
   (set KORU_BACKEND_TRACE=1 for the backend return trace)

Must fail at runtime:

Program must error when executed.

Error output must contain

Phantom state mismatch: argument 'c' has no tracked phantom state

Flows

flow ~read-raw click a branch to expand · @labels scroll to their anchor

read-raw (sensor_id: 1)

Test Configuration

MUST_ERROR

← 063 phantom state on primitive 065 phantom compound unit →