<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 26 August 2013 21:58, Nevin Liber <span dir="ltr"><<a href="mailto:nevin@eviloverlord.com" target="_blank">nevin@eviloverlord.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div class="im">On 26 August 2013 13:52, Ville Voutilainen <span dir="ltr"><<a href="mailto:ville.voutilainen@gmail.com" target="_blank">ville.voutilainen@gmail.com</a>></span> wrote:<br>
</div><div class="gmail_extra"><div class="gmail_quote"><div class="im">
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><br><div class="gmail_extra"><div class="gmail_quote"><div>I have strong reasons to believe we'll see an NB comment proposing std::less<br>
to be specialized for tuple<T*> and containers. </div></div></div></div></blockquote><div><br></div></div><div>What about tuple<T*&>? I'm thinking about what is returned from std::tie, as one quick way to implement a comparison operator for a user defined type is to compare the result of std::tie called on the appropriate member variables.<br clear="all">
</div></div></div></div></blockquote><div><br><div>I have strong reasons to believe references to pointers aren't covered by the aforementioned NB comment, but I expect<br></div>
the delegation head for that NB to nod approvingly if that case gets covered by tuple. <br><br></div></div><br></div></div>