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.
17 lines
832 B
Plaintext
17 lines
832 B
Plaintext
// issue 0105 / F3 — the const cycle guard must key on (name, AUTHOR-source), not
|
|
// name alone. `a.sx` declares `M :: 1` and `K :: M + 1` (= 2). `b.sx` flat-imports
|
|
// `a.sx` and declares a DIFFERENT same-name `M :: K + 1` (= 3) — so the SAME name
|
|
// `M` appears at two levels of one fold chain, in two different modules
|
|
// (b's `M` → a's `K` → a's `M`). A name-only cycle guard sees `M` twice and trips
|
|
// a FALSE cycle, folding b's `M` to null → the array dimension `[M]u8` becomes a
|
|
// non-const error. Keyed on (name, source) the two `M`s are distinct, so the
|
|
// chain folds: `m=3 len=3`, coherent for the value read and the dimension.
|
|
#import "modules/std.sx";
|
|
#import "0790-modules-same-name-const-cross-cycle-guard/b.sx";
|
|
|
|
main :: () -> i32 {
|
|
arr : [M]u8 = ---;
|
|
print("m={} len={}\n", M, arr.len);
|
|
0
|
|
}
|