On Wednesday, October 11, 2017, Kelvin Ma via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Yes, a 0-ary operator like that would have to be hard baked into the language itself.</div><div dir="ltr"></div></blockquote><div><br></div><div>Actually, you can just make a subscript which takes a function as an argument, and call it by passing in the ellipsis operator.</div><div><br></div>Nevin<span></span><br><div><br></div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"> Of course, the subscript notation has much more serious problems, there is no way to allow one-sided subscripting, but disallow two-sided subscripting for the memory API, while still allowing two-sided subscripting for ordinary slicing operations. This is why I still think <span style="font-family:monospace,monospace">at:from:</span> is the much better syntax.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 11, 2017 at 3:01 PM, Nevin Brackett-Rozinsky <span dir="ltr"><<a href="javascript:_e(%7B%7D,'cvml','nevin.brackettrozinsky@gmail.com');" target="_blank">nevin.brackettrozinsky@gmail.<wbr>com</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">I believe Kelvin was asking about the usage of ellipsis *by itself*, as in Xiaodi’s example, “newBuffer[...]”.<span><font color="#888888"><div><br></div><div>Nevin</div></font></span></div></blockquote></div></div>
</blockquote>