[ASDAlexander77]

What

Under -mm=own, a value read out of an assigned global can now be lent to a call unless the call may assign that global, or a global the pass cannot name.

Why

#639 refused any call that might drop anything once it was lent such a value. Only a store to the global releases its block, so G = new N(2); other(G), where other assigns a different global H, was rejected (the "#639 is coarse" half of own-raytrace follow-up 14).

rejectGlobalArgumentsDropped now reads __own_assigns_globals / __own_assigns_any_global. pinAssignedGlobals (#661) puts these on each call and runs just before the check. A callee that assigns the global itself, through another function, through a method or through a function value is still refused (new negative own_err_global_argument_indirect; the existing transitive and method negatives still pass).

own_err_global_kept_field is now refused by checkGlobalRead, the check that test was written for: keep stores the lent value into a field that outlives the next assignment of g. The test's comment and pinned message are updated to match.

Tests

• own_global_argument_other_global covers a callee, and a callee's callee, that assign another global. It runs under own, rc, gc and none.
• Full suite: Windows 5465 and Linux 5444, where the only failure was the old pin above. With the new pin, all 41 related tests pass on both systems; neither full suite was rerun after that.
• Own corpus on Linux: unchanged at 533, nothing lost.

🤖 Generated with Claude Code