<div dir="ltr"><br><div class="gmail_extra"><br><div class="gmail_quote">On Fri, May 12, 2017 at 9:09 AM, Dave Abrahams via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</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 class="gmail-HOEnZb"><div class="gmail-h5"><br>
on Sun May 07 2017, Pavol Vaskovic <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
<br>>> Drawback of this approach is that you need to use free function zip,<br>
> forcing a break in the chain of sequence operations, as there is currently<br>
> no zipped method on Sequence.<br>
><br>
>> If this is the preffered approach, we should consider removing the<br>
> enumerated() method altogether, because the limited usefullness in its<br>
> current state hardly justifies the space on API surface it occupies.<br>
<br>
</div></div>That is my preferred outcome.</blockquote><div><br></div><div>All right, so if I understand this correctly a SE to remove enumerated wold be in order.</div><div><br></div><div>I see following open questions:</div><div>* migration path to using zip + open range (can migrator handle it without introducing `zipped`?)</div><div>* performance impact (does zip + open range perform comparably to `EnumeratedSequence`?)</div></div><br></div><div class="gmail_extra">Am I forgetting something?</div><div class="gmail_extra"><br></div><div class="gmail_extra">--Pavol</div></div>