The language, from the ground up.

01 / Values, types and functions

let declares an inferred or explicitly typed variable; const prevents reassignment. Familiar types include int, float, bool, string, void, and fixed-width i8/i16/i32/i64 or u8/u16/u32/u64; usize/isize follow pointer width.

const name = "Noqeri"
let ready: bool = true
function triple(value: int): int = value * 3
print(triple(7))

02 / Control flow without ceremony

if and while accept conditions without parentheses. repeat N is counted-loop sugar. for value in fixedArray or slice has representative compiler and runtime tests, including break/continue behavior.

let total = 0
repeat 3 { total = total + 2 }
if total == 6 { print("ready") }

03 / Arrays, slices and scalar Lists

Use [T; N] for fixed arrays and []T for slices. Direct local scalar List<int>, List<float> and List<bool> growable operations are documented as partially qualified. Bounds errors currently trap, not a universal Result<T,E> recovery path.

let data: [int; 3] = [1,2,3]
for value in data { print(value) }

04 / Modules, records and generics

File imports resolve relative to the importing file and are compiled as a deduplicated graph. Records, typed pointers, fixed/slice arrays and constrained generic definitions exist, but general inference/ownership and native ABI parity are not universal.

import "math.noqeri"

function square(x: int): int {
    return x * x
}

05 / Errors, memory and unsafe operations

Some integer-status postfix ? and pointer ?? forms have differential evidence. General optional chaining ?. and fully typed Result<T,E> postfix propagation remain incomplete. Raw pointer arithmetic, volatile memory, atomics and inline assembly are systems-level features behind explicit safety/target restrictions.

06 / The compiler boundary

The C++ Stage-0 compiler and Noqeri-written NQRI bootstrap are distinct implementation paths. Do not infer universal backend parity from one passing language example.