> On Jul 12, 2016, at 8:47 AM, Erica Sadun via swift-evolution > <swift-evolution@swift.org> wrote: > > >> On Jul 11, 2016, at 4:49 PM, Chris Lattner <clatt...@apple.com >> <mailto:clatt...@apple.com>> wrote: >> >> As for all of the other additive changes, I would strongly prefer you to >> *wait* on even proposing or discussing these things until after the Swift >> 3.0 evolution cycle is done. Not only is it distracting for the community, >> but the core team and many others won’t be be able to even read the thread >> or the responses, thus your discussion cycle will be lacking key input. >> >> On this topic, we specifically discussed this when labeled breaks were being >> designed, and when they were expanded to “do” in Swift 2. We specifically >> decided to allow break but not continue, because we didn’t want these >> control flow statements to be “another way to spell a loop”. >> >> -Chris > > So I can take it as a given that this is out of scope for Swift 3 too? > > https://gist.github.com/erica/a78045d09fa5bb20e6e566295140c84d > <https://gist.github.com/erica/a78045d09fa5bb20e6e566295140c84d>
No, *that* is out of scope for *Swift*. - Doug
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution