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).
23 lines
718 B
Plaintext
23 lines
718 B
Plaintext
// Feature 1 — a pack element exposes ONLY the constraint protocol's interface.
|
|
// `xs[i].v` reaches a concrete field of IntCell that is not part of `Box`, so
|
|
// it's rejected even though IntCell does have `v` — a pack element is viewed
|
|
// through the protocol, like a constrained generic. (Protocol methods like
|
|
// `get()` ARE callable; see examples 193/194.)
|
|
|
|
#import "modules/std.sx";
|
|
|
|
Box :: protocol(T: Type) {
|
|
get :: (self: *Self) -> T;
|
|
}
|
|
IntCell :: struct { v: i64; }
|
|
impl Box(i64) for IntCell { get :: (self: *IntCell) -> i64 => self.v; }
|
|
|
|
leak :: (..xs: Box) -> i64 {
|
|
return xs[0].v; // `v` is not part of Box — error
|
|
}
|
|
|
|
main :: () -> i32 {
|
|
print("{}\n", leak(IntCell.{ v = 5 }));
|
|
0
|
|
}
|