Expressions
Pattern Matching
match performs exhaustive pattern matching. All cases must be covered.
fun main() -> i64 {
let value = 1;
match value {
1 => 10,
_ => 0,
}
}
Each arm body can be any expression, or a block. return/break/continue are
themselves expressions of type ! (see Break, Continue, and Return
below), so a bare arm body like 1 => return 10 needs no special grammar case —
it's just an ordinary expression arm, like any other:
// Match arm body forms start here.
fun classify(value: i64) -> i64 {
loop {
break match value {
0 => 0,
1 => return 10,
_ => { 20 },
};
}
}
fun main() -> i64 {
return classify(0);
}
match is an expression — all arms must produce the same type:
fun main() -> i64 {
let x = 1;
let label = match x {
0 => "zero",
1 => "one",
_ => "other",
};
return label.len();
}
Arms with blocks follow the same rules as function bodies: the block's tail expression (if present) is the arm's value; a block with no tail produces Unit.
enum Shape {
Circle { radius: f64 },
Rectangle { width: f64, height: f64 },
}
fun main() -> i64 {
let shape = Shape::Circle { radius: 3.0 };
let desc: String = match shape {
Shape::Circle { radius } => {
let area = radius * radius;
(area as i64).to_string()
},
Shape::Rectangle { width, height } => "rectangle",
};
return desc.len();
}
Pattern Kinds
| Pattern | Example | Matches |
|---|---|---|
| Wildcard | _ | anything, binds nothing |
| Binding | n | anything, binds to n |
| Literal | 0, "hi", true, None | exact value |
| Enum variant | Direction::North | unit variant |
| Enum with fields | Shape::Circle { radius } | variant, binds fields |
| Tuple | (a, b) | tuple, binds elements |
| Guard | n if n < 0 | binding + boolean condition |
Examples
// Pattern examples start here.
enum Shape {
Circle { radius: f64 },
Rectangle { width: f64, height: f64 },
}
fun main() -> i64 {
let shape = Shape::Rectangle { width: 4.0, height: 2.0 };
let x = -3;
let point: (i64, i64) = (0, 7);
let a = match shape {
Shape::Circle { radius } => radius as i64,
Shape::Rectangle { width, height } => width as i64,
};
let b = match x {
0 => 0,
n if n < 0 => 1,
_ => 2,
};
let c = match point {
(0, 0) => 0,
(x, 0) => x,
(0, y) => y,
(x, y) => x + y,
};
return a + b + c;
}
Control Flow
If / Else
fun main() -> i64 {
let condition = false;
let other = true;
if (condition) {
return 1;
} else if (other) {
return 2;
} else {
return 3;
}
}
if is also an expression (both branches must produce the same type):
fun main() -> i64 {
let x = 1;
let label = if (x > 0) { "positive" } else { "non-positive" };
return label.len();
}
Braceless bodies. A single expression may be used as the branch body without braces:
fun print_state() { }
fun main() -> i64 {
let debug = true;
let flag = false;
let value_a = 10;
let value_b = 20;
if (debug) print_state();
let x = if (flag) value_a else value_b;
return x;
}
The braceless form desugars to a single-expression block. Three restrictions apply:
- Arm style must be consistent. Both the
thenandelsearms must use the same style — either both braced or both braceless. Mixing is a parse error. - Dangling-else is forbidden. If the outer body is braceless, the body expression must not itself be an
if–else. Use braces on the outer body to resolve the ambiguity.fun main() -> i64 {let a = true;let b = false;if (a) if (b) { return 1; }if (a) { if (b) { return 2; } else { return 3; } }return 4;}fun main() {let a = true;let b = false;if (a) if (b) { return; } else { return; }} - No semicolon between braceless arms. Write
if (c) a else b;, notif (c) a; else b;— the;terminates the statement before theelse.
While
fun main() -> i64 {
var n = 3;
var total = 0;
while (n > 0) {
total += n;
n -= 1;
}
return total;
}
For
fun main() -> i64 {
var total = 0;
for (var i = 0; i < 4; i += 1) {
total += i;
}
return total;
}
For-In
Availability: Array and range iteration since v0.1.0. User-defined
Iterable<T>implementations since v0.4.0.
for-in works on any type implementing the Iterable<T> aspect. The loop variable
receives type T. T[], [T; N] (array and fixed-size array), and Range (produced by .. and ..=) implement
Iterable<T> by default. User-defined types can be made iterable by implementing
Iterable<T>. The loop binding is immutable by default and may be made loop-locally
mutable with var:
aspect Iterable<T> {
fun next(&var self) -> Perhaps<T>;
}
fun main() -> i64 {
return 0;
}
fun main() -> i64 {
let collection = [1, 2, 3];
var total = 0;
for (let item in collection) { total += item; }
for (var item in collection) {
item += 1;
total += item;
}
for (let i in 0..10) { total += i; }
for (let i in 0..=10) { total += i; }
return total;
}
References
Availability: Since v0.10.0.
References provide explicit aliasing for non-linear values.
fun main() -> i64 {
var n = 1;
let p: &var i64 = &var n;
p = 4; // write-through: p's own binding need not be `var` for this
return p; // type-directed copy: reads the value out at `return`
}
Rules:
&exprcreates a shared reference&Twhereexpris an addressable lvalue&var xcreates an exclusive reference&var Twherexis avaraddressable lvalue- there is no explicit dereference operator — access goes through auto-deref (below) or, for reading a plain value out with no field/method involved, type-directed copy (see Types — Reading a value out of a reference)
- assigning a plain value to a
&var T-typed binding writes through the reference — exclusivity comes from the reference, not the binding, so this holds whether or not the binding itself isvar(p = 4;above is exactly this, not a reassignment ofp—p's own binding has no annotation requiring it to bevarat all)
Addressable lvalues for both & and &var include named bindings (x), struct field access (s.field), tuple element access (t.0), array indexing (arr[i]), and chains thereof (nested.outer.field, t.1.0). Non-addressable expressions (call results, arithmetic) are rejected at runtime.
&var requires the operand to be a var binding — applying it to a plain let is a type error (T0006). &var on a lvalue path (&var s.field, &var arr[i]) produces a true exclusive reference with write-back semantics, matching &var on a named binding exactly — writes through it propagate to the original storage location (RFC-0045, already implemented; this section previously described &var struct.field as a non-propagating snapshot, which was the pre-RFC-0045 behavior and had never been updated to match). & on a field or element still evaluates to an independent, read-only reference to a copy of the current value at the time & was applied — correct and unchanged, since a shared reference is never written through.
Field access, field assignment, and method dispatch auto-dereference through a reference:
struct Counter {
value: i64,
}
extend Counter {
fun increment(&var self) {
self.value += 1;
}
}
fun main() -> i64 {
var counter = Counter { value: 0 };
let p: &var Counter = &var counter;
p.increment(); // auto-deref: equivalent to accessing through the reference directly
p.value = 1; // auto-deref field assign; the reference binding need not be var
return p.value; // auto-deref field read
}
Function references (&() -> T and &var () -> T) are callable directly, the same way:
fun main() -> i64 {
let f = () -> { return 42; };
let r: &() -> i64 = &f;
return r(); // auto-deref: calls through the reference directly
}
This applies uniformly: a closure or named function stored behind a reference can be called as if it were the function value itself. A common use is passing arrays of function references:
fun apply_all(fns: Array<&() -> ()>) {
for (let f in fns) {
f(); // auto-deref each element
}
}
Field access, method dispatch, and calling through a reference all chain through
multiple reference layers, not just one — rr: &&var Counter auto-derefs through both
levels to reach the Counter for a field read, a field write, or a method call
(&var self included: a shared outer layer doesn't remove the write access the inner
&var layer carries, it just adds a read-only step to reach it):
struct Counter { value: i64 }
extend Counter {
fun increment(&var self) { self.value += 1; }
}
fun main() -> i64 {
var c = Counter { value: 0 };
let p: &var Counter = &var c;
let rr: &&var Counter = &p;
rr.increment(); // auto-deref through both layers
return rr.value; // likewise for a field read
}
Indexing, argument passing, and assignment remain ordinary reference operations — none of them are the value-extraction case (see types.md), so none require type-directed copy.
Loop
loop creates an infinite loop. It is the only loop form that can produce a value:
fun main() -> i64 {
let result = loop {
break 42;
};
return result;
}
Typing rules:
loop { break expr; }has typeTwhereexpr: T. Allbreakarms must produce the same type.loop { }— a loop with no reachablebreak— has type!(Never). See Never Type.
Break, Continue, and Return
Availability: Since v0.10.0.
return, break, and continue are expressions of type ! (Never — see
Never Type), not statements. Since ! is a subtype of
every type, they're valid anywhere an expression is valid — a block tail with
no trailing ;, a braceless if-arm, a match-arm body, or nested inside
another expression — not just as a semicolon-terminated statement on its own
line:
fun pick(ok: boolean) -> i64 {
if (ok) return 42; // braceless if-arm, no braces needed
0
}
fun compute() -> i64 {
var i = 0;
loop {
i = i + 1;
if (i == 5) {
break i * 10 // loop-body tail, no trailing `;`
}
}
}
fun classify(value: i64) -> i64 {
match value {
0 => 0,
1 => return 10, // match-arm body, same as any other expression arm
_ => 20,
}
}
fun nested(c: boolean) -> i64 {
let x = if (c) return 99 else 0; // nested expression position
x
}
break exits the innermost loop; break expr exits a loop and produces
expr as the loop's value (break with no value produces Unit).
continue skips to the next iteration of the innermost loop. return/
return expr returns from the enclosing function, using the function's
declared return type (or Unit, if omitted):
fun returns_unit() {
return;
}
fun returns_value() -> i64 {
return 42;
}
fun main() -> i64 {
returns_unit();
return returns_value();
}