<div dir="ltr"><div>> <span style="font-size:12.8px">Is there a possibility for larger features like this or macros to be done in parallel with the 2.2/3.0 development effort? Or perhaps a desire to have this sort of working group approach (similar to C++’s Technical Subcommittees), but not until 3.0 is released?</span></div><div><span style="font-size:12.8px"><br></span></div><div>It's open source! Just make a public fork on GitHub, then other people can contribute if they desire. Discussion can take place on a separate GitHub issues if it would be too speculative for this list (can anything be too speculative for this list?).</div><div><br></div><div>The main problem right now seems to be that nobody has any clue how to even implement it.</div><div><br></div><div>- Alex</div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Dec 12, 2015 at 9:36 PM, David Waite 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word">I proposed it because <div>- Only a few named language features (like Concurrency) were explicit non-goals</div><div>- Its a feature I’m willing to try to implement (although I would probably want to work on several smaller changes to get up to speed first on SIL and the codebase)<br><div><br></div><div>Is there a possibility for larger features like this or macros to be done in parallel with the 2.2/3.0 development effort? Or perhaps a desire to have this sort of working group approach (similar to C++’s Technical Subcommittees), but not until 3.0 is released?</div><div><br></div><div>-DW</div><div><br><div><blockquote type="cite"><div><div class="h5"><div>On Dec 12, 2015, at 1:35 PM, Douglas Gregor via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br></div></div><div><div><div class="h5"><div style="word-wrap:break-word"><br><div><blockquote type="cite"><div>On Dec 11, 2015, at 10:48 PM, Kevin Ballard via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div>
<div><div>I'd love to have first-class support for generators like this, but it's a <i>lot</i> of work. It's a lot easier to do this sort of thing in a scripting language like Python than it is to do in a language like Swift, because it requires reifying the stack into a data structure that can be passed around. And I suspect there's a lot of non-trivial questions that have to get answered before you can even propose an implementation for this.<br></div>
<div> </div>
<div>For context, this sort of thing is something that people have been talking about doing in Rust for quite a while, and it keeps getting punted because of the amount of work and the unanswered questions about how it would actually be implemented.<br></div>
<div> </div>
<div>So I'll give this a general +1, but I think it should also be deferred until after Swift 3 at the earliest.</div>
</div></div></blockquote><div><br></div><div>Right. This is a major add-on feature that doesn’t fit in with the stated goals for Swift 3 (README of <a href="https://github.com/apple/swift-evolution" target="_blank">https://github.com/apple/swift-evolution</a>), so I think we should proactively defer it.</div><div><br></div></div><div><span style="white-space:pre-wrap"> </span>- Doug</div><br>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=nE9rxSXA5G4kxsTVkgv43vFcOQoCM-2FU-2BigXPSqPoICLxVE26HM-2Bto8xvhi-2Fe4Vr6G8Wc6HgfECMgWiW0on5x3epp4OqCYHA83s6pi6UIme7eiJGkU2ulwJe7TOcoyt-2FjrNysyr5Qdnz76rRaRJFu2JqyKLsR8K9FzWqJs-2BKnYpadUw-2B6xZ7mt6Exa-2BvNVFUY0Zrlcz2Bgwb38eRd3XbaInaqXzz39ScRYrNVrybNIXo-3D" alt="" width="1" height="1" border="0" style="min-height: 1px !important; width: 1px !important; border-width: 0px !important; margin: 0px !important; padding: 0px !important; display: none !important;">
</div></div></div><span class="">
_______________________________________________<br>swift-evolution mailing list<br><a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a><br><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br></span></div></blockquote></div><br></div></div>
<img src="https://u2002410.ct.sendgrid.net/wf/open?upn=ufQ1sKmNNtjEC-2BBUON-2BgZPd8t-2F4PFTin0qlI9lRM0AmIJTc7obJd14BwOUtWHNSkoaUjc-2FWh1QFbmIMgPKfGdQSK8jYcWWXAyJTFChwGEFAqJFiIKNNH-2B1uABx1mlDXGZHIuInt75qiMzMNWReUEFcq9V5CPfo5COV4IrC2oUgPDzG4hdph4zYvzMrxQ-2FPQCDLFx7OGug7seChyhA9CFStugIx0zlSzg-2F0d8LC69obM-3D" alt="" width="1" height="1" border="0" style="min-height: 1px !important; width: 1px !important; border-width: 0px !important; margin: 0px !important; padding: 0px !important; display: none !important;">
</div>
<br>_______________________________________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br>
<br></blockquote></div><br></div></div>