d8076b9333
Surface rename of the signed integer family: s1..s64 become i1..i64
(u1..u64, usize, isize unchanged). 'string' keeps the s-prefix arm in
name classification; width parsing moves to the i-prefix arm next to
isize.
Internal TypeId tags follow the surface (.s8/.s16/.s32/.s64 ->
.i8/.i16/.i32/.i64), as do mono-key mangle fragments (ptr_i64,
tu_i64_bool) and all display/diagnostic formatting (i{d}).
Migrated in the same sweep: stdlib + examples + issue repros + FFI C
companions (shared symbol names like ffi_id_i64), expected
stdout/stderr/ir snapshots, specs.md, readme.md, CLAUDE.md/AGENTS.md,
implementation_plan.md, docs/, issue writeups. Vendored stb_image and
historical flow state left untouched.
zig build test: 426/426; examples suite: 595/595.
16 lines
721 B
Plaintext
16 lines
721 B
Plaintext
// An array dimension that folds to a valid compile-time integer but exceeds a
|
|
// `u32` (`[5_000_000_000]i64`) is a hard error — a clean sx diagnostic with a
|
|
// non-zero exit, NOT a compiler panic.
|
|
//
|
|
// Regression (issue 0087 / F0.4 attempt 6): the dimension folded to a valid i64
|
|
// (5e9) and was then narrowed with an unchecked `@intCast` to u32, aborting the
|
|
// COMPILER with "integer does not fit in destination type". Every dim/lane fold
|
|
// now narrows through the single range-checked `program_index.foldDimU32`, which
|
|
// reports an out-of-u32-range dimension as this diagnostic and halts the build.
|
|
#import "modules/std.sx";
|
|
|
|
main :: () {
|
|
a : [5000000000]i64 = ---;
|
|
print("unreachable: {}\n", a.len);
|
|
}
|