Type tuple pointers

Timon Gehr via Digitalmars-d digitalmars-d at puremagic.com
Thu May 21 09:14:31 PDT 2015


On 05/21/2015 06:14 PM, Timon Gehr wrote:
> On 05/21/2015 06:05 PM, Alex Parrill wrote:
>> On Thursday, 21 May 2015 at 15:37:42 UTC, Dicebot wrote:
>>> On Thursday, 21 May 2015 at 15:30:59 UTC, Alex Parrill wrote:
>>>> They aren't types themselves, so `TypeTuple!(int, char) var` doesn't
>>>> make sense.
>>>
>>> Sadly, you are wrong on this one - this is actually a valid variable
>>> declaration which will create two distinct local variables and uses
>>> their aliases in resulting symbol list named 'var'.
>>
>> So it creates a variable for each type in the tuple, and stores the
>> aliases in `var`? Huh, didn't know that.
>>
>> But still, `TypeTuple!(int,char)` isn't a real type, so having a pointer
>> to one doesn't make sense.
>
>
> Well, one might somewhat sensibly treat Seq!(char,char)* as
> Seq!(char*,char*). :o)

Meant to say Seq!(int,char)* -> Seq!(int*,char*).


More information about the Digitalmars-d mailing list