[swift-evolution] Swift 4 evolution mailing list for not Swift 2.x/Swift 3 suitable proposals (async/await, for example)

[Chris Lattner]

On Jan 30, 2016, at 12:31 PM, Craig Cruden via swift-evolution <swift-evolution at swift.org> wrote:
> Items that are interesting and deferred may theoretically impact ideas that will be implemented in Swift 3.  

My NVHO on this topic:

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.

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.

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.

-Chris



> 
>> On 2016-01-31, at 3:30:11, Craig Cruden <ccruden at novafore.com <mailto:ccruden at novafore.com>> wrote:
>> 
>> 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…. 
>> 
>> Once Swift 3 is out the door these deferred items would be re-reviewed.
>> 
>> 
>>> On 2016-01-31, at 3:28:24, Radosław Pietruszewski via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>> 
>>> My understanding is that we should, well… await the release of Swift 3.
>>> 
>>> 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.
>>> 
>>> — Radek
>>> 
>>>> On 30 Jan 2016, at 21:25, Vanderlei Martinelli via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>>>> 
>>>> Hello everybody.
>>>> 
>>>> 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?
>>>> 
>>>> Regards,
>>>> -- Vanderlei Martinelli
>>>> _______________________________________________
>>>> swift-evolution mailing list
>>>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>>>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
>>> 
>>> _______________________________________________
>>> swift-evolution mailing list
>>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>>> https://lists.swift.org/mailman/listinfo/swift-evolution <https://lists.swift.org/mailman/listinfo/swift-evolution>
>> 
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160130/f052ceea/attachment.html>