6b0ebdd92b
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).
19 lines
702 B
Plaintext
19 lines
702 B
Plaintext
// Phase 6 — `mapper(..sources.value)`: project a method over a pack and spread
|
|
// the results into a closure call. The mapper lambda's params are contextually
|
|
// typed from the `Closure(...)` parameter even though `apply` is a pack-fn.
|
|
|
|
#import "modules/std.sx";
|
|
|
|
VL :: protocol(T: Type) { get :: (self: *Self) -> T; }
|
|
IntCell :: struct { v: i64; }
|
|
impl VL(i64) for IntCell { get :: (self: *IntCell) -> i64 => self.v; }
|
|
|
|
apply :: (mapper: Closure(i64, i64) -> i64, ..sources: VL) -> i64 {
|
|
return mapper(..sources.get); // (a, b) => a + b applied to (i0.get(), i1.get())
|
|
}
|
|
|
|
main :: () -> i32 {
|
|
print("{}\n", apply((a, b) => a + b, IntCell.{ v = 40 }, IntCell.{ v = 2 })); // 42
|
|
0
|
|
}
|