Hello downs,
retard wrote:
Thu, 10 Dec 2009 01:01:34 +0100, downs wrote:
including such gems as incorrect
tuple lengths, incorrect tuple slices, endless errors without line
numbers, spurious template instantiation errors with nonsensical
parameters, and at least one case where T[0] evaluated to T,
necessitating the workaround Tuple!(T[0])[0], it felt appropriate.
Why are these needed? Because of compiler bugs?
Apparently, in certain very specific corner cases, my version of GDC
believes that when I say "T[0]", I really mean "T". In that case,
"Tuple!(T[0])[0]" is like saying "really very the first element". :)
I call it a Bug. Do you have a test case?
