Protocol method declarations now declare their receiver explicitly as the first parameter — 'self: *Self' (or 'self: Self') — matching the impl method signature, instead of the old implicit-receiver form where the listed params were only the extra args. That asymmetry repeatedly caused confusion over whether the first param was the receiver or an argument. The parser validates the first param is 'self' typed Self/*Self, then strips it, so all downstream lowering and the dispatch ABI are unchanged (impl blocks and call sites are unaffected). A protocol method missing the receiver is now a parse error. Migrated all 129 protocol method signatures across library + examples (+ one inline-sx test in sema.zig) to the explicit form. Updated specs.md + readme.md. New: examples/0418-protocols-explicit-receiver.sx (feature), examples/1190-diagnostics-protocol-missing-receiver.sx (negative/diagnostic).
29 lines
942 B
Plaintext
29 lines
942 B
Plaintext
// Feature 1 — value-position pack projection: `xs.<method>` projects a
|
|
// (zero-arg) protocol method over every element into a TUPLE of the per-element
|
|
// results. For a parameterised `Box(T)`, each element's method returns its own
|
|
// `T`, so the projected tuple is heterogeneous.
|
|
//
|
|
// xs.get ≈ (xs[0].get(), xs[1].get())
|
|
|
|
#import "modules/std.sx";
|
|
|
|
Box :: protocol(T: Type) {
|
|
get :: (self: *Self) -> T;
|
|
}
|
|
|
|
IntCell :: struct { v: i64; }
|
|
StrCell :: struct { s: string; }
|
|
impl Box(i64) for IntCell { get :: (self: *IntCell) -> i64 => self.v; }
|
|
impl Box(string) for StrCell { get :: (self: *StrCell) -> string => self.s; }
|
|
|
|
show :: (..xs: Box) -> void {
|
|
vals := xs.get; // tuple (i64, string)
|
|
print("0={} 1={}\n", vals.0, vals.1);
|
|
}
|
|
|
|
main :: () -> i32 {
|
|
show(IntCell.{ v = 42 }, StrCell.{ s = "hi" });
|
|
show(StrCell.{ s = "x" }, IntCell.{ v = 7 }); // order swapped → (string, i64)
|
|
0
|
|
}
|