Date: Sat, 18 Apr 2026 09:26:23 -0700
On Saturday, 18 April 2026 07:24:12 Pacific Daylight Time Muneem via Std-
Proposals wrote:
> 2. What I meant, by "tuples have overhead" is that they have a fixed ABI
> for all their specaizations, which means that any book keeping has to be on
> the top of the tuple and can't be inside it. Since runtime indexed tuples
> are a completely different notion than compile indexed tuple since one is a
> product type like a struct. Runtime indexed tuples is heterogeneous list. A
> product type is not a product type if it has anything other than the
> objects of the multiple types it holds.
And why does it have to be inside, instead of outside? You clearly believe
that to be the case, but you have not proven it or given a basis for why it
should be so. What is the benefit of having the book-keeping at all?
Proposals wrote:
> 2. What I meant, by "tuples have overhead" is that they have a fixed ABI
> for all their specaizations, which means that any book keeping has to be on
> the top of the tuple and can't be inside it. Since runtime indexed tuples
> are a completely different notion than compile indexed tuple since one is a
> product type like a struct. Runtime indexed tuples is heterogeneous list. A
> product type is not a product type if it has anything other than the
> objects of the multiple types it holds.
And why does it have to be inside, instead of outside? You clearly believe
that to be the case, but you have not proven it or given a basis for why it
should be so. What is the benefit of having the book-keeping at all?
-- Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org Principal Engineer - Intel Data Center - Platform & Sys. Eng.
Received on 2026-04-18 16:26:28
