<html><head><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=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 11, 2016, at 4:49 PM, Chris Lattner <<a href="mailto:clattner@apple.com" class="">clattner@apple.com</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=""><div class="">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.</div><div class=""><br class=""></div><div class="">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”.</div><div class=""><br class=""></div><div class="">-Chris</div></div></div></blockquote><br class=""></div><div>So I can take it as a given that this is out of scope for Swift 3 too?</div><div><br class=""></div><div><a href="https://gist.github.com/erica/a78045d09fa5bb20e6e566295140c84d" class="">https://gist.github.com/erica/a78045d09fa5bb20e6e566295140c84d</a></div><div><br class=""></div><div><br class=""></div><div>-- E</div><div><br class=""></div><br class=""></body></html>