[ASDAlexander77]

Fixes #459.

Under rc and own, a module-level let G: Node | null = mk() was freed at start. The initializer passes the call's result to ts.GlobalResult through a cast to the union. That cast is the call's only use, and a releasable one, so the call's reference was given back at the end of the region as a discarded temporary. The global then pointed at freed memory. A plain let G = mk() passes the call to the terminator directly, so it was fine.

claimHandleGlobalInitializers already made exactly this claim for Shared<T> handles (own spec 23.1). It is renamed claimGlobalInitializers and now covers every global whose type owns a block. When a producer carrying an owned reference is reached through ts.Cast, ts.OptionalValue or ts.CreateUnionInstance, it is marked consumed, and the global keeps its count.

The retain for a handle read out of a field or element stays handle-only, because under own a retain left in a global's region is an error for any other type.

Tests

• New 00global_union_from_call.ts:
  • It covers Node | null let and const globals and a Node | undefined global, each initialised from a call, read after allocations of the same size have reused anything freed, then reassigned.
  • It is registered as compile and JIT tests and in the rc/none corpus.
  • It failed under rc before the change.
• The -mm=rc/own: a Node | null global initialised from a call is freed at start #459 repro now prints made1 under rc and own; before, it printed k1 and k26.
• The own corpus is unchanged: 453 / 593 plain, 451 / 593 with --opt, same files.
• Full Release ctest: 3636/3637. The one failure is test-compile-gc-defaultlib-collector, the known local LNK2005 against the stale installed default library, which fails the same way on main.

Not covered here: #461, a global object literal { s: mk() }. There the call's result is stored into a field of the literal's temporary rather than reaching the global through a view, so it needs its own fix.

🤖 Generated with Claude Code