Skip to main content
Next (unreleased) · docs c218d875 · core f63c1e69 · built 2026-10-26 22:39 UTC

Tuples have no rest pattern or spread over their numeric-label row

Gap​

A tuple cannot be split into its first element and the rest, or extended, in a generic body. If RFC-0151 makes tuples rows with numeric labels, RFC-0178's forms could apply, but whether (a, ..rest) yields a re-indexed tuple (rest.0 is the old .1) or keeps the original labels is that RFC's decision, not RFC-0178's.

Impact​

Visible to Metel programmers: variadic-style tuple code (a head/tail) has no generic spelling; use a record or a fixed arity.

Affects​

Resolution​

Not scheduled. Decide together with RFC-0151.