Bindings and Control Flow

Source boundary: This page summarizes the Edition 1 documentation shipped with nebo-v1.1.0. It is a reading guide, not a fresh execution test or a compatibility guarantee for your compiler.

Names and mutability

The binding grammar describes a dot followed by an identifier, with an optional .mutable suffix. In the versioned language tour, values are bound by expression suffixes and mutable counters are marked explicitly. A name’s spelling and type constraints matter; a parsed binding is not permission to mutate every value.

Conditions and loops

The language tour uses a parenthesized while condition. The loop reference describes a conditionless loop block and records a bounded example with if, break and a mutable counter. Its rejection case places break outside a loop.

These references explain specific admitted forms. They do not establish that every combination of branching, mutation, ownership and early exit works on your compiler.

When diagnosing a program

Separate syntax errors from type errors and invalid mutation. Preserve the failing source and compiler diagnostics before simplifying it. For a comparison case, use the complete source and expected result in the versioned reference, including any module inputs.

Next: functions and modules.