s/type tuple/template pack/g please

Brad Anderson eco at gnuk.net
Wed Aug 21 11:48:07 PDT 2013


On Wednesday, 21 August 2013 at 18:45:49 UTC, Andrei Alexandrescu 
wrote:
> On 8/21/13 11:44 AM, Brad Anderson wrote:
>> On Wednesday, 21 August 2013 at 18:26:42 UTC, Andrei 
>> Alexandrescu wrote:
>>> On 8/21/13 11:21 AM, Brad Anderson wrote:
>>>> On Wednesday, 21 August 2013 at 17:53:21 UTC, Andrei 
>>>> Alexandrescu wrote:
>>>>> There's an inordinate amount of confusion around what we 
>>>>> currently
>>>>> call "type tuple" (embodied in std's TypeTuple). I've been 
>>>>> furious
>>>>> immediately as I got word that Walter called it that way, 
>>>>> and it
>>>>> hasn't failed to make everybody else feel the same over the 
>>>>> years.
>>>>>
>>>>> So: shall we use "template pack" going forward exclusively 
>>>>> whenever we
>>>>> refer to that stuff? That way we can unambiguously use 
>>>>> "tuple" for
>>>>> "value tuples, i.e. like mini-structs that group values 
>>>>> together".
>>>>>
>>>>> Destroy. I mean criticize.
>>>>>
>>>>>
>>>>>
>>>>> Andrei
>>>>
>>>> There are a lot of good names for it: Template Pack, Type 
>>>> Sequence,
>>>> Template Argument List, Type List, etc. I think I like Type 
>>>> Sequence the
>>>> best but any will do.  All that really matters is getting 
>>>> Tuple out of
>>>> the name to clear up the confusion.
>>>
>>> We much more need to get "type" out of the name. Those aren't 
>>> types.
>>>
>>> Andrei
>>
>> Alright. I always found the Tuple part more confusing but I 
>> guess I'm in
>> the minority since three people all jumped on the "type" 
>> portion of my
>> comment at once.
>
> "Tuple" needs to go as well, although that entity does look 
> like a tuple in some respects.
>
> Andrei

Yeah, the name "tuple" isn't actually all that inaccurate.  The 
problem is more that it places too much load on the word for two 
very distinct things.


More information about the Digitalmars-d mailing list