Records & Tuples (R&T) was a TC39 proposal for two new value types:
- a Record,
#{ x: 1, y: 2 }, like an object, and - a Tuple,
#[1, 2, 3], like an array.
They were to be primitives: typeof would report "record" and "tuple", they could contain only primitives and other records and tuples (an object inside threw a TypeError), so they were deeply immutable, and === compared them by content. #{ a: 1 } === #{ a: 1 } would be true, so they'd work directly as Map keys.
It reached Stage 2 and then stalled. Ashley Claymore's February 2025 summary to TC39 records the constraints it hit: any design must not add new primitives, and there was no appetite to overload === with content comparison. The same talk relayed a committee view that values which look like objects and arrays but aren't objects would confuse JavaScript users. At the April 2025 plenary the committee agreed to withdraw it; TC39's inactive-proposals list now says Subsumed by Composites.
Composites is the successor, at Stage 2 as of October 2026. It keeps the main use case, compound keys, but within those constraints: a composite is an ordinary frozen object, it can hold any value (so it's only shallowly immutable), and equal composites are treated as the same key by Map and Set. The current draft does this by interning, so equal composites are literally the same object; the README warns the design will change.
Until then, the language has only objects compared by identity. You build immutability from Object.freeze (shallow), TypeScript's readonly (compile time only), or libraries, and you build compound keys by hand.