<div dir="ltr">I wouldn't mind a std::tuple inside the iterator, if that turns out to be the easiest/tidiest solution - could totally be.<br><br>My concern was about adding global op overloads to tuple and/or otherwise trying to make tuple itself into an iterator. Seemed like it could be problematic.</div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Aug 3, 2015 at 1:20 PM, Pete Cooper <span dir="ltr"><<a href="mailto:peter_cooper@apple.com" target="_blank">peter_cooper@apple.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word"><br><div><span class=""><blockquote type="cite"><div>On Aug 3, 2015, at 11:07 AM, Duncan P. N. Exon Smith <<a href="mailto:dexonsmith@apple.com" target="_blank">dexonsmith@apple.com</a>> wrote:</div><br><div><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:14px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">I have the same twitch... it seems dangerous somehow to add API to</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:14px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:14px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">std::tuple.  I think adding our own class (that wraps a `std::tuple<...>`)</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:14px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:14px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">would feel safer, I guess because it's more explicit.  Kind of on the</span><br style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:14px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px"><span style="font-family:Helvetica;font-size:12px;font-style:normal;font-variant:normal;font-weight:normal;letter-spacing:normal;line-height:14px;text-align:start;text-indent:0px;text-transform:none;white-space:normal;word-spacing:0px;float:none;display:inline!important">fence myself though.</span></div></blockquote><div><br></div></span><div>So i totally understand the bad feeling from the operator overloads.  I can change those to be helper methods.</div><div><br></div>However, I think I misread David’s original email.  I thought he didn’t like the use of std::tuple at all.  David, mind clarifying?</div><div><br></div><div>In particular, "avoid the quirk and implement a custom iterator that wraps all the other iterators" sounds to me like trying to find a way to avoid having a std::tuple inside the iterator.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>Pete</div><br></font></span></div></blockquote></div><br></div>