<div dir="ltr"><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">I&#39;d like to see concrete discussion of the fact(?) that all view-adaptors currently inherit from view_interface. Is that an accident of vendor-implementation? or an accident of specification? or is it really deliberate and we can rely on it not to change in the future?</blockquote><div><br></div><div>This should definitely be worth discussing.</div><div>It seems <a href="https://cplusplus.github.io/LWG/issue3549">LWG 3549</a> needs to be mentioned (even though I didn&#39;t initially intend to do so), after which I think inheriting `view_interface` may be an option over inheriting `view_base` *in any way*, even though the former may not currently be able to synthesize any functions through the base class (also see my naive SO question back in the day: <a href="https://stackoverflow.com/questions/69303724/why-does-basic-istream-view-inherit-view-interface">Why does `basic_istream_view` inherit `view_interface?`</a>, and ironically, my <a href="https://cplusplus.github.io/LWG/issue3715">LWG 3715 </a> proved the answer. :) )<br></div><div><br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">In the proposed wording, `ranges::distance` should be `ranges::size`. (They do the same physical thing in this case, but the latter better reflects your intent.)</blockquote><div><br></div><div>I personally prefer `ranges::distance`, which avoids the implicit conversion (i.e. difference type) before comparing with an index value, but `ranges::size` definitely sounds reasonable, and perhaps this should be decided by the LWG. I&#39;ll add a discussion for this.</div><div><br></div><div>Thanks again for the valuable feedback! </div><div><br></div><div>Hewill</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Arthur O&#39;Dwyer &lt;<a href="mailto:arthur.j.odwyer@gmail.com">arthur.j.odwyer@gmail.com</a>&gt; 於 2023年11月16日 週四 上午10:41寫道：<br></div><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 dir="ltr">On Wed, Nov 15, 2023 at 8:42 PM Hewill Kang via Std-Proposals &lt;<a href="mailto:std-proposals@lists.isocpp.org" target="_blank">std-proposals@lists.isocpp.org</a>&gt; wrote:</div><div class="gmail_quote"><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><span lang="en"><span><span>I&#39;ve written a draft proposal for </span></span></span>`<span lang="en"><span><span>view_interface::at</span></span></span>` in </div><div><a href="https://htmlpreview.github.io/?https://github.com/hewillk/view_interface-at/blob/main/view-at.html" target="_blank">https://htmlpreview.github.io/?https://github.com/hewillk/view_interface-at/blob/main/view-at.html</a></div></div></blockquote><div><br></div><div>I suggest that the first word of the proposal shouldn&#39;t be &quot;Finally&quot;. :)</div><div><br></div><div>I&#39;d like to see concrete discussion of the fact(?) that all view-adaptors currently inherit from view_interface. Is that an accident of vendor-implementation? or an accident of specification? or is it really deliberate and we can rely on it not to change in the future?</div><div>I.e., I&#39;d like you to list out a bunch of view-adaptors and view-factories (at least these four: <b>take_while_view, iota_view, subrange, common_view</b>) and show how deliberate is the wording that makes them inherit from view_interface. Or if there&#39;s already some kind of blanket wording that says &quot;All standard view adaptors inherit from view_interface...&quot;, that&#39;s even better, and should be mentioned.</div><div><br></div><div>In the proposed wording, `ranges::distance` should be `ranges::size`. (They do the same physical thing in this case, but the latter better reflects your intent.)</div><div><br></div><div>Other than that, seems reasonable to me.</div><div><br></div><div>Cheers,</div><div>Arthur</div></div></div>
</blockquote></div>

