<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Jan 13, 2016 at 4:52 PM, Richard Smith <span dir="ltr"><<a href="mailto:richard@metafoo.co.uk" target="_blank">richard@metafoo.co.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div class="gmail_extra"><div class="gmail_quote"><span class="">On Wed, Jan 13, 2016 at 2:31 PM, Nathan Wilson <span dir="ltr"><<a href="mailto:nwilson20@gmail.com" target="_blank">nwilson20@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">nwilson added a comment.<br>
<span><br>
In <a href="http://reviews.llvm.org/D15421#326144" rel="noreferrer" target="_blank">http://reviews.llvm.org/D15421#326144</a>, @rsmith wrote:<br>
<br>
> Bikeshedding on the name a bit... how about `__type_pack_element`?<br><br>
</span>Hmm, I kind of felt like having `nth` in there implied we're indexing into something... What about `__nth_pack_element`?</blockquote><div><br></div></span><div>Conversely, std::nth_element doesn't do indexing, and std::tuple_element does.</div></div></div></div></blockquote><div><br></div><div>Yeah, I was trying to combine them, but maybe that's misleading. </div></div><br></div></div>