Rename all example tests/companions to the XXXX-category-test-name scheme (per-category 100-blocks: basic 0010, types 0100, ... errors 1000, diagnostics 1100, ffi 1200, ffi-objc 1300, ffi-jni 1400, vectors 1500, platform 1600). Companions and dir/C fixtures move in lockstep with their parent test; #import/#source/#include paths rewritten to match. Expected output now lives in examples/expected/ (a sibling dir of the tests) split into three streams per the new convention: <name>.exit / <name>.stdout / <name>.stderr (+ optional <name>.ir) run_examples.sh rewritten: scans examples/ and issues/ for an expected/<name>.exit marker, captures stdout and stderr separately (no more 2>&1), compares each stream + exit + optional IR snapshot. Behavior validated unchanged: every renamed test reproduces its prior merged output + exit (diffs limited to file paths/basenames embedded in diagnostics + traces, which correctly reflect the new names). Suite: 292 passed, 0 failed. 50-smoke.sx split + issue relocation + docs follow in subsequent commits.
40 lines
1.4 KiB
Plaintext
40 lines
1.4 KiB
Plaintext
// Variadic heterogeneous type packs — control-flow follow-up to
|
|
// issue-0045 fix (commit 9e78790).
|
|
//
|
|
// issue-0045's fix routes inline-comptime-body `return X;` into a
|
|
// result slot so the caller's basic block isn't terminated
|
|
// mid-flight. But the fix sets `block_terminated = true` after
|
|
// the inline return — which leaks PAST the enclosing `if`'s
|
|
// merge block. When the body shape is
|
|
// if cond { return X; }
|
|
// return Y;
|
|
// only the then-branch's `return X;` runs; `block_terminated`
|
|
// stays true in the merge block, so `lowerBlockValue`'s loop
|
|
// exits before the trailing `return Y;` lowers. The trailing
|
|
// return never stores into the slot — for the false-condition
|
|
// path the load reads uninitialised stack memory.
|
|
//
|
|
// Pack-fn `..$args` is the shortest repro because `args.len`
|
|
// gives a comptime-feeling test for the condition. The bug is
|
|
// actually shape-agnostic — any comptime body with `if cond
|
|
// { return X; }; return Y;` regresses the same way.
|
|
//
|
|
// `maybe()` with zero call-args takes the false branch and
|
|
// should fall through to `return -1;`. Today it loads garbage
|
|
// from the uninitialised slot.
|
|
|
|
#import "modules/std.sx";
|
|
|
|
maybe :: (..$args) -> s64 {
|
|
if args.len > 0 {
|
|
return 42;
|
|
}
|
|
return -1;
|
|
}
|
|
|
|
main :: () -> s32 {
|
|
print("{}\n", maybe()); // expect -1
|
|
print("{}\n", maybe(99)); // expect 42
|
|
return 0;
|
|
}
|