<div dir="ltr">Well, I’d like to congratulate you and your team for the Swift language. I think it is the best programming language we have today and I really enjoy coding in Swift (it was love at first sight). Protocol extensions and error handling are blowing mind things you added in version 2, amongst other nice features. :-)<div><br></div><div>As a system/software architect, however, I have the habit of thinking of the projects in the short, medium and long term as I think you do too. I’m programming in Swift since the day-zero of the first public beta release and since this I try to convince the teams I work to adopt Swift too. When they ask me about Swift 3 and future versions, now I have something to say. Nevertheless they ask: “After the next conversion process will we need to rewrite important parts of the code and test them one more time spending weeks with this again like we did with previous versions?” And I have to answer: “Yes. But only we want access to latest Swift, Apple SDK and and third-party framework features." Of course we want!</div><div><br></div><div>I know that resilience is a goal of your team and it is not a easy thing to accomplish. But the example of `async` and `await` is a feature that me and others are asking since pre-RC 1.0 versions. I think that @Craig suggestion is a very good one. Some things have, I think, to have its discussion started very early in the process to guide the long term development. This is my opinion, of course (as I’m writing it).</div><div><br></div><div>Regards,</div><div><br></div><div>-Van</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sat, Jan 30, 2016 at 7:52 PM, Chris Lattner 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"><span class="">On Jan 30, 2016, at 12:31 PM, Craig Cruden via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</span><div><span class=""><blockquote type="cite"><div><div style="word-wrap:break-word">Items that are interesting and deferred may theoretically impact ideas that will be implemented in Swift 3. </div></div></blockquote><div><br></div></span><div>My NVHO on this topic:</div><div><br></div><div>I don’t think there is any point in discussing features beyond Swift 3 now, and I think it would be harmful to do so. There isn’t enough bandwidth from the core team to participate in these discussions, and we’d like to keep the rest of the community and contributors focused on what is important to make Swift 3 great.</div><div><br></div><div>What happens in Swift 3 will inform what happens in Swift 4. While there are some things that we can predict (e.g. concurrency being a feature) there are many completely different design directions that may prove out to be the best. It is extremely unlikely that a discussion right now would shed any light on the tradeoffs involved that would select the best approach, but it is very likely that a lot of discussion time would be wasted.</div><div><br></div><div>I know it requires patience and restraint, but it really is best for everyone involved to wait until the right time to have these discussions. This Fall (for the northern hemisphere) is not that far away and there is a ton of important work to do now.</div><span class="HOEnZb"><font color="#888888"><div><br></div><div>-Chris</div></font></span><span class=""><div><br></div><div><br></div><br><blockquote type="cite"><div><div style="word-wrap:break-word"><div><br><div><blockquote type="cite"><div>On 2016-01-31, at 3:30:11, Craig Cruden <<a href="mailto:ccruden@novafore.com" target="_blank">ccruden@novafore.com</a>> wrote:</div><br><div><div style="word-wrap:break-word">I would think that they would get discussed here then end up with a status of deferred, which would mean - interesting idea that would like to happen but priorities prevent it from happening…. <div><br></div><div>Once Swift 3 is out the door these deferred items would be re-reviewed.</div><div><br></div><div><br><div><div><blockquote type="cite"><div>On 2016-01-31, at 3:28:24, Radosław Pietruszewski via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div style="word-wrap:break-word"><div>My understanding is that we should, well… <b>await</b> the release of Swift 3.</div><div><br></div><div>Makes little sense to discuss features in abstract that won’t get the needed attention from the core team until Swift 3 is out the door.</div><br><div>
<div>— Radek</div>
</div>
<br><div><blockquote type="cite"><div>On 30 Jan 2016, at 21:25, Vanderlei Martinelli via swift-evolution <<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>> wrote:</div><br><div><div dir="ltr">Hello everybody.<div><br></div><div>I would like to discuss things like `async` and `await` for Swift, but I know this not fit the current Swift 3 scope. Where we can start to discuss Swift 4 proposals?</div><div><br></div><div>Regards,</div><div>-- Vanderlei Martinelli</div></div>
_______________________________________________<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></div></blockquote></div><br></div>_______________________________________________<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></div></blockquote></div><br></div></div></div></div></blockquote></div><br></div></div>_______________________________________________<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></div></blockquote></span></div><br></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>