Martin has just merged the rename of `TypeTuple` to `AliasSeq` into the stable branch, which will be released soon. If anyone wants to change the name again, please open a PR immediately, this is the last chance.

On Friday, 24 July 2015 at 08:51:04 UTC, Marc Schütz wrote:
> Martin has just merged the rename of `TypeTuple` to `AliasSeq` into the stable branch, which will be released soon. If anyone wants to change the name again, please open a PR immediately, this is the last chance.

Here are the final results of the poll if any one cares...
AliasTuple		3.083333333
AliasList		2.85
Aliases			2.716666667
AliasSeq		2.55
AliasPack		2.516666667
Pack			2.266666667
TemplateArgumentList 	2.15
Arguments		2.066666667
TypeTuple		2.016666667
CtTuple			1.983333333
ArgPack			1.9
ParamPack		1.833333333
ArgumentsTuple		1.783333333
AliasArray		1.766666667
AliasSplat		1.716666667
CompileTimeTuple	1.716666667
Splat			1.683333333
Identities		1.6
Tuple			1.566666667
Identity		1.55
AliasGroup		1.466666667
List			1.416666667
AliasSet		1.416666667
TemplateSplat		1.4
MixedList		1.4
OmniSplat		1.35
AliasBag		1.266666667
AliasLine		1.166666667
Bag			1.166666667
AliasBall		1.133333333
AliasPile		1.133333333
AliasBeads		1.1

On Friday, 24 July 2015 at 10:35:35 UTC, Tofu Ninja wrote:
> On Friday, 24 July 2015 at 08:51:04 UTC, Marc Schütz wrote:
>> Martin has just merged the rename of `TypeTuple` to `AliasSeq` into the stable branch, which will be released soon. If anyone wants to change the name again, please open a PR immediately, this is the last chance.
>
> Here are the final results of the poll if any one cares...
> AliasTuple		3.083333333
> AliasList		2.85
> Aliases			2.716666667
> AliasSeq		2.55

Even though I personally favor tuple, 'Aliases' has the "extra umph that the BDFL favors it" as well as scoring higher in the poll than 'AliasSeq'.

On Friday, 24 July 2015 at 10:35:35 UTC, Tofu Ninja wrote:
> On Friday, 24 July 2015 at 08:51:04 UTC, Marc Schütz wrote:
>> Martin has just merged the rename of `TypeTuple` to `AliasSeq` into the stable branch, which will be released soon. If anyone wants to change the name again, please open a PR immediately, this is the last chance.
>
> Here are the final results of the poll if any one cares...
> AliasTuple		3.083333333
> AliasList		2.85
> Aliases			2.716666667
> AliasSeq		2.55

Why is the poll at odds with the supposed-to-be-final decision?

On Monday, 27 July 2015 at 01:52:34 UTC, Enamex wrote:
> On Friday, 24 July 2015 at 10:35:35 UTC, Tofu Ninja wrote:
>> On Friday, 24 July 2015 at 08:51:04 UTC, Marc Schütz wrote:
>>> Martin has just merged the rename of `TypeTuple` to `AliasSeq` into the stable branch, which will be released soon. If anyone wants to change the name again, please open a PR immediately, this is the last chance.
>>
>> Here are the final results of the poll if any one cares...
>> AliasTuple		3.083333333
>> AliasList		2.85
>> Aliases			2.716666667
>> AliasSeq		2.55
>
> Why is the poll at odds with the supposed-to-be-final decision?

Because the decision is not going to be made based on a popularity contest, and many of the folks who have been discussing this have not voted in that poll. Also, there is no clear winner in the poll anyway. AliasTuple is slightly ahead, but remember that _5_ was the top, not 3. So, the ones at the "top" of the list are far from being universally liked.

AliasTuple in particular has serious issues with it from the perspective of teaching people what it is an how to use it, because it has Tuple in its name, and the construct in question is not actually a tuple (in addition to being easily confused with std.typecons.Tuple). This has been shown time and time again with TypeTuple.

On technical merit, AliasSeq is one of the better choices; it was what TypeTuple had been changed to prior to the recent, large discussion on it; and none of the new suggestions are better enough to win any kind of consensus. At this point, for it to be changed, Walter and Andrei need to step in and choose something else. Otherwise, it's just going to stay AliasSeq, and it will be final, because we're not changing it again after 2.068 goes out. But thus far, they haven't changed it and have let it stay as AliasSeq, and the window of time for them to change it is shrinking fast. Regardless, even if the decision were to be made based on the poll, it would be Walter and Andrei making that decision, because it is abundantly clear that the community is unable to come to a consensus on this.

- Jonathan M Davis

On Monday, 27 July 2015 at 02:14:57 UTC, Jonathan M Davis wrote:
> On technical merit, AliasSeq is one of the better choices; it was what TypeTuple had been changed to prior to the recent,

On technical merits "Seq" is one of the worst choices, let's not confuse social dynamics with objectivity.

On Monday, 27 July 2015 at 02:14:57 UTC, Jonathan M Davis wrote:
> AliasTuple in particular has serious issues with it from the perspective of teaching people what it is an how to use it, because it has Tuple in its name,

People keep claiming that, but have never posted any evidence. We know that _TypeTuple_ had issues, but for all we know, the problem was the "Type" part, not the "Tuple" part.

> and the construct in question is not actually a tuple

And that's IMO another really bizarre claim. Of course it's a tuple.

> (in addition to being easily confused with std.typecons.Tuple). This has been shown time and time again with TypeTuple.
>
> On technical merit, AliasSeq is one of the better choices; it was what TypeTuple had been changed to prior to the recent, large discussion on it; and none of the new suggestions are better enough to win any kind of consensus.

If ease of learning / avoidance of misunderstandings is a goal, it's clear that AliasSeq is one of the worst choices. The term "sequence" - in all other related areas of science or engineering - invokes certain associations that don't fit this thing at all. This has been brought up by several people, but it's just getting ignored by the proponents.

As for Andrei and Walter: From what I've seen, they, too, agree that AliasSeq is bad. Andrei's critique even started that other thread.

On Monday, 27 July 2015 at 02:14:57 UTC, Jonathan M Davis wrote:
> Because the decision is not going to be made based on a popularity contest, and many of the folks who have been discussing this have not voted in that poll. Also, there is no clear winner in the poll anyway. AliasTuple is slightly ahead, but remember that _5_ was the top, not 3. So, the ones at the "top" of the list are far from being universally liked.
>
> AliasTuple in particular has serious issues with it from the perspective of teaching people what it is an how to use it, because it has Tuple in its name, and the construct in question is not actually a tuple (in addition to being easily confused with std.typecons.Tuple). This has been shown time and time again with TypeTuple.
>
> On technical merit, AliasSeq is one of the better choices; it was what TypeTuple had been changed to prior to the recent, large discussion on it; and none of the new suggestions are better enough to win any kind of consensus. At this point, for it to be changed, Walter and Andrei need to step in and choose something else. Otherwise, it's just going to stay AliasSeq, and it will be final, because we're not changing it again after 2.068 goes out. But thus far, they haven't changed it and have let it stay as AliasSeq, and the window of time for them to change it is shrinking fast. Regardless, even if the decision were to be made based on the poll, it would be Walter and Andrei making that decision, because it is abundantly clear that the community is unable to come to a consensus on this.
>
> - Jonathan M Davis

Just food for thought, the difference between the rating of AliasTuple and AliasSeq is the same as the difference between AliasSeq and TypeTuple....

On 07/27/2015 10:12 AM, "Ola Fosheim =?UTF-8?B?R3LDuHN0YWQi?= <ola.fosheim.grostad+dlang@gmail.com>" wrote:
> On Monday, 27 July 2015 at 02:14:57 UTC, Jonathan M Davis wrote:
>> On technical merit, AliasSeq is one of the better choices; it was what
>> TypeTuple had been changed to prior to the recent,
>
> On technical merits "Seq" is one of the worst choices, let's not confuse
> social dynamics with objectivity.
>

Your particular flavour of objectivity.

On Monday, 27 July 2015 at 09:01:33 UTC, Marc Schütz wrote:
> On Monday, 27 July 2015 at 02:14:57 UTC, Jonathan M Davis wrote:
>> AliasTuple in particular has serious issues with it from the perspective of teaching people what it is an how to use it, because it has Tuple in its name,
>
> People keep claiming that, but have never posted any evidence. We know that _TypeTuple_ had issues, but for all we know, the problem was the "Type" part, not the "Tuple" part.
>

We have various reports that are consistent and confirm this is an issue. At this point, this is a repeatable experiment, not an anecdote anymore. Ignoring repeatable experiment puts you in the tinfoil hat section of the population. You don't want to be there.

>> and the construct in question is not actually a tuple
>
> And that's IMO another really bizarre claim. Of course it's a tuple.
>

Technically you are right. But in fact, this is NOT what people EXPECT a tuple to be.

>> (in addition to being easily confused with std.typecons.Tuple). This has been shown time and time again with TypeTuple.
>>
>> On technical merit, AliasSeq is one of the better choices; it was what TypeTuple had been changed to prior to the recent, large discussion on it; and none of the new suggestions are better enough to win any kind of consensus.
>
> If ease of learning / avoidance of misunderstandings is a goal, it's clear that AliasSeq is one of the worst choices. The term "sequence" - in all other related areas of science or engineering - invokes certain associations that don't fit this thing at all. This has been brought up by several people, but it's just getting ignored by the proponents.
>

It is not ignored. It is simply that alternative proposal also have issues, and many of them have issues that are worse. No proposal was significantly better so that it reached any kind of consensus.

No your personal favorite did not either.

> As for Andrei and Walter: From what I've seen, they, too, agree that AliasSeq is bad. Andrei's critique even started that other thread.

Yet, nobody came with anything significantly better, so here it is.