Files
sx/examples/1337-ffi-objc-call-11-bool-return.sx
agra bdd0e96d78 feat(lang): block value requires no trailing ; (Rust-style)
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).
2026-06-02 09:23:50 +03:00

49 lines
1.9 KiB
Plaintext

// Backfill for Phase 1D cluster 1.28 (PLAN-FFI.md): `#objc_call(bool)`
// against `BOOL`-returning selectors. Obj-C `BOOL` is single-byte on
// every Apple ABI we ship to (signed char on i386, native `bool` on
// arm64), so the slot shape is identical to `#objc_call(u8)` — this
// test is about the source-level type being meaningful, not a
// distinct ABI path.
//
// Two IMPs are installed: `yes_imp` returns true, `no_imp` returns
// false. Both are dispatched through `#objc_call(bool)` and the
// results are checked.
#import "modules/std.sx";
#import "modules/compiler.sx";
#import "modules/std/objc.sx";
yes_imp :: (self: *void, _cmd: *void) -> bool callconv(.c) { true }
no_imp :: (self: *void, _cmd: *void) -> bool callconv(.c) { false }
main :: () -> s32 {
inline if OS == .macos {
// Nil-recv: libobjc returns a zeroed slot, which decodes as false.
nil_b := #objc_call(bool)(null, "isEqual:");
print("nil bool = {}\n", nil_b);
ns_object := objc_getClass("NSObject".ptr);
my_cls := objc_allocateClassPair(ns_object, "SxBoolProbe".ptr, 0);
// BOOL type-encoded as `B` (C99 _Bool) in `B@:` — implicit
// (self: id, _cmd: SEL) return BOOL. Some toolchains prefer
// `c` (signed char) for BOOL on i386, but `B` is unambiguous
// on arm64 and works for runtime-registered IMPs.
sel_yes := sel_registerName("yes".ptr);
sel_no := sel_registerName("no".ptr);
class_addMethod(my_cls, sel_yes, xx yes_imp, "B@:".ptr);
class_addMethod(my_cls, sel_no, xx no_imp, "B@:".ptr);
objc_registerClassPair(my_cls);
instance := class_createInstance(my_cls, 0);
y := #objc_call(bool)(instance, "yes");
n := #objc_call(bool)(instance, "no");
print("yes = {}\n", y);
print("no = {}\n", n);
}
inline if OS != .macos {
print("skipped (not macos)\n");
}
0
}