<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Dec 13, 2015, at 4:24 PM, Dmitri Gribenko via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div dir="ltr" class=""><div class="gmail_extra"><div class="gmail_quote">On Sun, Dec 13, 2015 at 3:43 PM, Michael Henson via swift-evolution <span dir="ltr" class=""><<a href="mailto:swift-evolution@swift.org" target="_blank" class="">swift-evolution@swift.org</a>></span> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr" class="">Currently, the construct:<br class=""><br class="">for x in something {}<div class=""><br class="">expects "something" to be a SequenceType. From that variable, the underlying code retrieves a generator by calling something.generate(). The resulting GeneratorType instance is unavailable to calling code.<br class=""><br class="">Unless there is a reason for the language to require a SequenceType, it seems like there are good use cases for accepting a caller-provided GeneratorType, too.<br class=""></div></div></blockquote><div class=""><br class=""></div><div class="">I support this. We would need to define what happens when the expression is both a generator and a sequence, but otherwise I don't see why not.</div></div></div></div></div></blockquote><div><br class=""></div>When the language is able to handle recursive protocol requirements, this will become redundant, because GeneratorType will refine SequenceType (with generate returning self). So, IMO, this isn't a problem worth solving separately.</div><div><br class=""></div><div class="">
-Dave<div class=""><br class=""></div><br class="Apple-interchange-newline">
</div>
<br class=""></body></html>