On Thu, Aug 15, 2013 at 11:18:21PM -0700, Jonathan M Davis wrote: [...] > You should probably read this article if you haven't: > > http://dlang.org/tuple.html > > Unfortunately, it muddles things a fair bit, because it uses Tuple > instead of std.typetuple.TypeTuple, and then it talks about expression > tuples vs type tuples (whereas a TypeTuple could be either an > expression tuple or a type tuple), but that just highlights how > confusing this is and how badly named TypeTuple is (but unfortunately, > it's used in so much code now, that renaming it just isn't going to > happen). That article should probably be rewritten so that it takes > TypeTuple into account. But it does contain some good info if you can > properly understand the difference between TypeTuple and a type tuple. > > - Jonathan M Davis
On Fri, Aug 16, 2013 at 02:32:08PM +0200, Dicebot wrote: > dlang.org documentation on this topic is quite confusing, > unfortunately. There was a small discussion in this > http://d.puremagic.com/issues/show_bug.cgi?id=10803 bug report > recently where Kenji has surprised me a lot with explanation how > this really is intended to work. Argh, can somebody *pretty please* submit a pull to fix the docs? It's things like this that turns newbies away ("What's this? The docs contradict each other! I don't understand this language! Hmm let's look at the next language on the list"). I would do it myself, except that after reading Kenji's notes on #10803 I'm no longer so sure I understand it myself. :-/ T -- One Word to write them all, One Access to find them, One Excel to count them all, And thus to Windows bind them. -- Mike Champion
