<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"><meta http-equiv="content-type" content="text/html; charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""><br class=""><!-- signature open -->Sent from my iPhone<!-- signature close --></div><div class=""><br class="">On Dec 12, 2015, at 1:36 PM, David Waite <<a href="mailto:david@alkaline-solutions.com" class="">david@alkaline-solutions.com</a>> wrote:<br class=""><br class=""></div><blockquote type="cite" class=""><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class="">I proposed it because <div class="">- Only a few named language features (like Concurrency) were explicit non-goals</div></div></blockquote><div class=""><blockquote type="cite" class=""><div class=""><div class="">- 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 class=""><div class=""><br class=""></div><div class="">Is there a possibility for larger features like this or macros to be done in parallel with the 2.2/3.0 development effort? </div></div></div></blockquote><div class=""><br class=""></div><div class="">Yes, design and experimental implementation can certainly proceed on the side. However, we are bandwidth-constrained on how much design we can do, so (for example) the core team may not be able to engage as deeply as we would like and we would not be able to bring a proposal for a review until time permits. Swift 3 is pretty ambitious as is, and losing focus can be a serious problem for a release.</div><div class=""><br class=""></div><blockquote type="cite" class=""><div class=""><div class=""><div class="">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></div></blockquote><div class=""><br class=""></div><div class="">We can evaluate this again at some point, but I don't want to "fan out" to having multiple working groups until we've had more experience with this process through Swift 3. In part, this is because of my experiences with the ISO C++ process. Particularly now, where there are a significant number of active subgroups in the C++ committee, it is very hard to even keep track of all of the different pieces under discussion, much less establish and maintain a coherent vision going forward. And that’s in a fairly mature language (C++) where the community has had a longer time to get a feel for what the language is; it’s harder for a younger language like Swift where the philosophy isn’t as widely understood.</div><div class=""><br class=""></div> - Doug</div><div class=""><br class=""><blockquote type="cite" class=""><div class=""><div class=""><div class=""><br class=""></div><div class="">-DW</div><div class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 12, 2015, at 1:35 PM, Douglas Gregor 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=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 11, 2015, at 10:48 PM, Kevin Ballard 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="">
<title class=""></title>
<div class=""><div class="">I'd love to have first-class support for generators like this, but it's a <i class="">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 class=""></div>
<div class=""> </div>
<div class="">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 class=""></div>
<div class=""> </div>
<div class="">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 class=""><br class=""></div><div class="">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" class="">https://github.com/apple/swift-evolution</a>), so I think we should proactively defer it.</div><div class=""><br class=""></div></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><br class="">
<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="height:1px !important;width:1px !important;border-width:0 !important;margin-top:0 !important;margin-bottom:0 !important;margin-right:0 !important;margin-left:0 !important;padding-top:0 !important;padding-bottom:0 !important;padding-right:0 !important;padding-left:0 !important;" class="">
</div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></div></div></blockquote></div></body></html>