On Monday, 19 August 2013 at 17:22:26 UTC, H. S. Teoh wrote:
What I'd like to know, is how all of these proposals address the
fundamental differences between "symbol tuples" (compile-time
construct) and std.range.Tuple (runtime construct). As far as I
can tell, people are still confusing the two, and it's really
not helping. Before we solve this, any syntax suggestion seems
more like a mortician's work than a real solution.
As far as I can tell, when everyone talks about tuple syntax,
they are talking about run-time tuples. That's definitely what
I'm talking about whenever I mention tuple syntax, as I don't
think it would be a good thing to use it for both run-time and
compile-time tuples (and I don't really consider the latter
tuples).
Bearophile has mentioned a couple times that we could use the
tuple syntax for both, and bring about a unification of these two
tuple types. I don't like this, as they're both very different
entities, and don't really have any relation to each-other
whatsoever.
I think the best course of action is to keep TypeTuples as is
(and possibly provide a new name for them, underdocumenting or
outright deprecating the old name), and introduce the new syntax
for run-time tuples.
Speaking of new names for TypeTuple, I don't know if this was
mentioned already, but what about "Variadic Lists"?
