Reference

Error Codes

A lookup table for VNE diagnostics, grouped by compiler phase and runtime policy.

Diagnostics are emitted with a stable VNE-* code, a severity, a source location, an excerpt, and optional suggestions. Codes in the VNE-010–VNE-032 range are mostly informational notes emitted when a ruleset is applied.

Lexer and parser

CodeMeaning
VNE-001Unexpected token
VNE-002Missing semicolon
VNE-003Unknown type name
VNE-005Unresolved import
VNE-006Malformed numeric literal (hex or float)
VNE-007Integer literal overflow
VNE-008Unexpected character

Rulesets and diagnostics

CodeKindMeaning
VNE-010noteWarnings enabled
VNE-011noteDynamic casting enabled
VNE-012noteMemory-limit tracking enabled
VNE-013errorUnknown ruleset flag
VNE-014errorValue expected for a ruleset key
VNE-015noteMemory limit set
VNE-016warningUnknown ruleset value
VNE-017errorInvalid warning level
VNE-020warningUnknown ruleset flag
VNE-021noteValid type_check modes
VNE-022warningUnknown type_check mode
VNE-023noteValid implicit_casting modes
VNE-024noteProfiling enabled
VNE-025noteProfiling disabled
VNE-026noteDebug mode enabled
VNE-027noteTrace mode enabled
VNE-028noteMax iterations set
VNE-029noteType-check mode hint
VNE-030noteWarnings disabled hint
VNE-031notePedantic mode enabled
VNE-032noteVerbose mode enabled

Generics, interfaces, and declarations

CodeMeaning
VNE-040Malformed interface type-parameter list
VNE-041Interface type parameter is not a simple identifier
VNE-042Malformed function type-parameter list
VNE-043Function type parameter is not a simple identifier
VNE-050Expected commit, commit_if, or move after region.
VNE-060Invalid scratch element type
VNE-061Scratch dimension is not positive or not a valid expression
VNE-062Struct scratch without @layout<soa>
VNE-063Invalid @layout mode or whole-element SoA access
VNE-100Method table full (VYNE_MAX_METHODS = 4096)

Regions and scratch

CodeKindMeaning
VNE-070errorRegion escape: assigning region-local storage to a shallower variable
VNE-071errorScratch shape mismatch or invalid single index on rank > 1
VNE-072runtimeScratch index out of bounds
VNE-080errorInvalid region policy argument, composition, or target
VNE-081errorInvalid policy argument token
VNE-082runtimePool/slab/ring/streamed capacity exceeded
VNE-083error/runtimeIntrinsic misuse (drop, move, pool/slab/ring/streamed alloc/free, persistent nesting)
VNE-084errorcommit / move on a stack-allocated scratch array
VNE-085errorcommit_if outside @speculative
VNE-086errorQualified commit across a nesting level
VNE-089errorInvalid @realtime argument
VNE-090runtimeanalog_write_resolution above 8 (clamped)
VNE-091runtimePin has no external interrupt
VNE-101error@bounded compile-time violation (static scratch or bad argument)
VNE-102runtime@bounded exceeded at runtime (arena or VLA)
VNE-106error@deterministic region contains a time/RNG source
VNE-107errorreturn inside @zeroed / @deterministic
VNE-108errorreturn inside @bounded
VNE-109runtime@realtime deadline overrun

Contracts

CodeKindMeaning
VNE-111runtimerequires / ensures / @invariant violation
VNE-112errorMalformed contract or @invariant
VNE-113warningUnknown contracts mode

Automatic differentiation

CodeMeaning
VNE-120Function outside the supported @differentiable subset
VNE-121Unsupported statement or mutation inside @differentiable
VNE-122–VNE-125Unsupported expression or grad() misuse
VNE-126backward() could not resolve the recorded differentiable call
VNE-127Malformed newton_solve() call or residual outside the implicit scalar subset
VNE-128Runtime implicit solve failure (non-convergence or singular dF/dz)

Reading a diagnostic

Every diagnostic in the terminal prints:

  • the severity (error, warning, note, perf hint);
  • the code, which you can look up here;
  • the message;
  • the source location (file:line);
  • a short excerpt with a caret at the column;
  • zero or more suggestions when the compiler has a specific fix.

If a code is missing from this page, treat that as a documentation bug: the compiler's diagnostics are the source of truth.

AVR-specific runtime diagnostics

On the Arduino target, some desktop fprintf + exit paths become serial output followed by a halt:

  • VNE-072 scratch bounds — vyne_panic_bounds
  • VNE-102 @bounded — vyne_panic_region_bound
  • VNE-109 @realtime — serial message and halt
  • VNE-111 contract violation — serial message and halt

See also