On Tuesday, 28 July 2015 at 11:50:09 UTC, Marc Schütz wrote:
Sorry, but this is unhelpful. All you are saying here is that
"TypeTuple" is bad. Yes, but we already know that. Everyone
agrees on that.
The real question is: _What exactly_ is the problem with
TypeTuple? The "Type" part of the name? The "Tuple" part? The
combination? Maybe it's not the name at all, but the concept,
or only some part of its behaviour?
Nothing in your post gives us a clue which kind of name would
be better. In particular, it doesn't show that `AliasSeq` is
any better than `TypeTuple`. So we're changing it from a bad
name to one that could be even worse, for all we know.
It seems you and deadalnix actually have useful evidence that
can answer these questions, but neither of you posted them.
Please do!
Honestly when I first was learning D, the Type part of TypeTuple
was the part messed me up. I had a rough idea what a tuple was
though never need to use one, so the Tuple part seemed to make
sense to me, but the Type part always confused the crap out of me.
