bdd0e96d78
A block's value is now its last statement ONLY when that statement is a trailing expression with no `;`. A trailing `;` discards the value, leaving the block void. This makes value-vs-statement explicit and lets the compiler reject "this block was supposed to produce a value". Compiler: - Parser records `Block.produces_value` (last stmt is a no-`;` trailing expression) + `Block.discarded_semi` (the `;` that discarded a value), via `expectSemicolonAfter`. A trailing expression before `}` may now omit its `;` (previously a parse error). Match-arm and else-arm bodies are built value-producing regardless of the arm `;` (arms are exempt — the `;` is an arm terminator). - Lowering: `lowerBlockValue` / the block-expr path / `inferExprType` respect `produces_value`. A value-position block that discards its value is a hard error (`lowerValueBody` for function bodies; the value-context `.block` path for if/else branches, `catch` bodies, value bindings, match arms). Pure-failable `-> !` bodies (value rides the error channel) and a value-if whose branches are void are handled without false errors. - `defer`/`onfail` cleanup bodies lower as statements (void), so a trailing `;` there is fine. Migration (behavior-preserving — output unchanged): - stdlib + ~210 examples: dropped the trailing `;` on value-position last expressions. `format` now ends with an explicit `#insert "return result;"` (it relied on `#insert`-as-block-value, which `;` discards). - Two `main :: () -> s32` examples that relied on the old silent default-return got an explicit trailing `0`. - Rejection snapshots 0412 / 1013 regenerated (their quoted source lines lost a `;`); the diagnostics themselves are unchanged. Docs/tests: specs.md "Block values" section; examples 0040 (rules) + 0041 (rejection); 3 parser unit tests. Filed issue 0066 (pre-existing match-arm negated-literal phi-width quirk, surfaced not caused here). Gates: zig build, zig build test, run_examples.sh -> 343 passed, cross_compile.sh -> 7 passed (also refreshed its stale example names).
51 lines
1.7 KiB
Plaintext
51 lines
1.7 KiB
Plaintext
// ffi-objc-arc-01 — M4.A smoke test for NSObject + autoreleasepool.
|
|
//
|
|
// Exercises:
|
|
// 1. NSObject is declared in std/objc.sx and reachable from user code.
|
|
// `obj.retain()` / `obj.release()` dispatch via the M2.3 #extends-aware
|
|
// method chain. Pattern: `defer obj.release();` as the canonical
|
|
// sx idiom for owned Obj-C handles.
|
|
// 2. `autoreleasepool(body)` stdlib helper wraps `body` in a
|
|
// push/defer-pop pair so Foundation factory returns drain at block
|
|
// end.
|
|
//
|
|
// macOS-only — libobjc + NSObject must be available at runtime.
|
|
|
|
#import "modules/std.sx";
|
|
#import "modules/std/objc.sx";
|
|
#import "modules/compiler.sx";
|
|
|
|
main :: () -> s32 {
|
|
inline if OS == .macos {
|
|
// Manual retain/release on an NSObject instance — the
|
|
// `defer obj.release();` pattern is the canonical sx idiom.
|
|
obj := NSObject.alloc().init();
|
|
if obj == null { print("FAIL: alloc null\n"); return 1; }
|
|
defer obj.release();
|
|
|
|
// Bump the count and drop the extra; refcount math stays balanced.
|
|
_ = obj.retain();
|
|
obj.release();
|
|
|
|
print("retain/release: ok\n");
|
|
|
|
// autoreleasepool helper round-trip — just exercise that the
|
|
// push/pop pair executes. We don't have a side-effect to observe
|
|
// (NSObject.new returns a +1 retained, NOT autoreleased), so this
|
|
// is a smoke test of the helper's shape, not the runtime
|
|
// behavior.
|
|
autoreleasepool(() => {
|
|
inner := NSObject.new();
|
|
if inner != null {
|
|
inner.release();
|
|
}
|
|
});
|
|
|
|
print("autoreleasepool: ok\n");
|
|
}
|
|
inline if OS != .macos {
|
|
print("skipped (not macos)\n");
|
|
}
|
|
0
|
|
}
|