Good to see another bad name merged in master ^_^

On Wednesday, 15 July 2015 at 07:50:46 UTC, Dicebot wrote:
> Good to see another bad name merged in master ^_^

Personally, I'm ok with the name AliasTuple
Though I thought AliasSplat was good though...

Also, this seems like the longest bikeshedding thread yet, even longer than the official bikeshedding thread a couple weeks ago!

On Wednesday, 15 July 2015 at 07:59:49 UTC, wobbles wrote:
> On Wednesday, 15 July 2015 at 07:50:46 UTC, Dicebot wrote:
>> Good to see another bad name merged in master ^_^
>
> Personally, I'm ok with the name AliasTuple
> Though I thought AliasSplat was good though...

Well if you forget for a moment that it is neither tuple (per std.typecons.Tuple semantics) nor limited to aliases... :D

> Also, this seems like the longest bikeshedding thread yet, even longer than the official bikeshedding thread a couple weeks ago!

AFAIR it is third thread like that on this topic in last 2 or 3 years.

On Wednesday, 15 July 2015 at 07:50:46 UTC, Dicebot wrote:
> Good to see another bad name merged in master ^_^

Yep, same feeling here....

--
Paolo

On Wednesday, 15 July 2015 at 08:13:20 UTC, Paolo Invernizzi wrote:
> On Wednesday, 15 July 2015 at 07:50:46 UTC, Dicebot wrote:
>> Good to see another bad name merged in master ^_^
>
> Yep, same feeling here....

At this point, I think that it's simply a question of which bad name we go with. None of them are particularly good, and there's a lot of disagreement about almost all of them - and if there's a lot of agreement, it's about how bad the name is, not how good it is.

I'd be very surprised to ever get real agreement on this. There simply isn't a good name for it. And if Walter and Andrei like AliasTuple, it's probably going to stick (and Andrei does seem to like it; no idea about Walter).

- Jonathan M Davis

On Wednesday, 15 July 2015 at 07:50:46 UTC, Dicebot wrote:
> Good to see another bad name merged in master ^_^

Was there a good name suggested that wasn't vetoed by Walter or Andrei?

On Wednesday, 15 July 2015 at 07:50:46 UTC, Dicebot wrote:
> Good to see another bad name merged in master ^_^

I don't mind AliasTuple, TypeTuple implied it could only contain types.

The main issue is that the documentation for tuples is incredibly confusing.

On Wednesday, 15 July 2015 at 08:05:59 UTC, Dicebot wrote:
> Well if you forget for a moment that it is neither tuple (per std.typecons.Tuple semantics) nor limited to aliases... :D

My first association with 'Tuple' is that it's a heterogeneous structure, this is clearly a step up compared to other alternatives which were discussed such as 'Array' which traditionally are homogeneous.

Thus I'm in favour of this name.

On Wednesday, 15 July 2015 at 08:29:52 UTC, Mike wrote:
> On Wednesday, 15 July 2015 at 07:50:46 UTC, Dicebot wrote:
>> Good to see another bad name merged in master ^_^
>
> Was there a good name suggested that wasn't vetoed by Walter or Andrei?

For me it was absolutely clear that picking a good name is impossible even through the previous discussion (~1 year ago) because existing semantics is a mess and breaking it is out of question. Thus more realistic criteria is name consistency with some bit of fact correctness.

This was how original (Meta)List was chosen - being as bad as any other, it matched terms used by official compiler spec : http://dlang.org/template.html#TemplateParameterList http://dlang.org/template.html#TemplateArgumentList (and related docs)

It is mostly irrelevant though (as long as it is not fundamentally misleading) - the whole issue is not about picking a single name but major cleanup sweeps through dlang.org and Phobos ensuring it is all on same terms and any possible abmiguity is clearly explained.

On Wednesday, 15 July 2015 at 09:32:07 UTC, Dicebot wrote:

> This was how original (Meta)List was chosen - being as bad as any other, it matched terms used by official compiler spec : http://dlang.org/template.html#TemplateParameterList http://dlang.org/template.html#TemplateArgumentList (and related docs)
>
> It is mostly irrelevant though (as long as it is not fundamentally misleading) - the whole issue is not about picking a single name but major cleanup sweeps through dlang.org and Phobos ensuring it is all on same terms and any possible abmiguity is clearly explained.

Your comment resonates with me.  Would TemplateArguments, TemplateArgs, or TemplateArgList make things any better in your opinion?

FYI, I didn't expect the AliasTuple PR to be merged so quickly.  If that's as good as it gets, so be it, but I'd like to bring this discussion to a amicable end, and I don't mind submitting a couple more alternate PRs if will help those who have to make the final judgment call and bring this issue to a close.

Mike