The canonical sx block-body lambda is `(params) { stmts }` (and
`(params) -> Ret { stmts }`); the arrow form `=>` is for EXPRESSION bodies
(`(params) => expr`). The arrow-block hybrid `(params) => { .. }` was being
used in 33 files — convert all of them by dropping the `=>`. The two forms are
exactly equivalent (verified: identical IR and identical runtime values — the
block tail is the value with or without a `-> Ret`), so this is a pure source
cleanup: no `.ir` churn, and the only snapshot change is 0923's diagnostic
COLUMN (a negative narrowing test whose error span shifted by the removed `=> `).
Arrow EXPRESSION bodies (`=> expr`, `=> .{..}`, `=> [..]`) and `=>` inside
comments/strings were left untouched. Migrated across examples/concurrency,
examples/{closures,ffi-objc,generics,optionals,types}, issues/, and the stdlib
(io.sx, sched.sx). Suite 855/0.
16 lines
625 B
Plaintext
16 lines
625 B
Plaintext
// `sleep(ms)` rejects a NEGATIVE duration loudly — the virtual clock is
|
|
// monotonic (advances only as timers fire), so a negative deadline would rewind
|
|
// it and break every ordering contract. Regression (B1.4b review, P2-c): the
|
|
// guard aborts instead of silently arming a past deadline.
|
|
//
|
|
// aborts (exit 134) after the diagnostic — aarch64-macOS-pinned.
|
|
#import "modules/std.sx";
|
|
sched :: #import "modules/std/sched.sx";
|
|
main :: () -> i64 {
|
|
s := sched.Scheduler.init(); ps := @s;
|
|
ps.spawn(() { ps.sleep(10); ps.sleep(-5); }); // -5 → loud abort
|
|
s.run();
|
|
print("unreachable\n");
|
|
return 0;
|
|
}
|