GO COMPILER TIGHTENS RANGE-CLEAR SAFETY CHECKS

The range-clear optimization, which replaces manual loops with direct object clearing, has been restricted to prevent data corruption [1]. The fix requires the range index to remain stack-local and ensures the index itself doesn't appear in the target being cleared, stopping later iterations from accidentally selecting different objects. In parallel, the compiler's disjointness analysis now uses types recorded during Store operations rather than relying on separate type tracking [2], tightening memory safety guarantees across the optimization pipeline. Together, these changes represent Go's continuing effort to make high-performance optimizations safer by default. The compiler team has now built in protections that catch edge cases where optimization assumptions break down.