[ASDAlexander77]

What

Under -mm=own, a tuple or record that holds owned objects can now be used as a value. This removes three refusals of that one shape.

Shape	Before	Now
[mk(1), mk(2)] as [N, N], built in a local or returned	refused: "takes a second reference"	own builds it in a slot, as an object literal is built (createTupleInSlot), and reads that as the literal taking each value
const r = rec(); r.a.x + r.b.x	refused: the first ts.ExtractProperty moved the record, so the second read was "used here after its value was moved"	a field that is only read counts as a read of the record (fieldOnlyRead), and so does each read of that field, so a use after the record is moved is still caught
let [a, b] = pair()	refused	each let borrows its field until the record is released, the same way a let already borrows a temporary (fieldTakersOf in checkValueMoves); decideRetains skips the retains that borrow already erased

A tuple of literals or of existing reads ([1, "a"], [[1, "x"], 2], [items[1]]) is still one ts.CreateTuple. The check uses own_facts::isConstantData and looks through casts and views. Other memory models are unchanged.

Still refused

Each is pinned by a new negative test:

• returning a record's field (own_err_record_field_returned);
• returning a destructured local (own_err_destructured_field_returned);
• reading a field after the record went to a callee that keeps it (own_err_record_field_after_move);
• reading a field of a spec-32 borrowing record after its argument is overwritten (own_err_borrowing_record_const_field).

Tests

• own_tuple_record_values runs under own (including the no-counting check) and under rc, gc and none.
• Own corpus on Linux: 535 → 537 files accepted (00tuple_runtime_arrays, arrayLiterals3), both giving the same output as gc under MALLOC_PERTURB_. None lost.
• Full suite: Windows 5509/5509, Linux 5488/5488.

🤖 Generated with Claude Code