--- Comment #5 from 2011-07-23 05:23:06 PDT ---
(In reply to comment #3)

> This is keeping consistent feature.
> Current D allow compilation of following code:
> TypeTuple!(int, int) f = 10;
> assert(f[0] == 10);
> assert(f[1] == 10);

I didn't know this, thank you. So the semantics of TypeTuple is broken. This
design mistake must not be carried over to Tuples too. Consistancy with a so
wrong design is like shooting yourself in the foot and makes this whole
enhancement request of negative value.

It's better to fix this TypeTuple design bug instead. I will file an
enhancement request on it.

Configure issuemail:
------- You are receiving this mail because: -------

Reply via email to