<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 Dec 10, 2015, at 6:47 AM, Amir Michail <<a href="mailto:a.michail@me.com" class="">a.michail@me.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=""><br class=""><div class=""><blockquote type="cite" class=""><div class="">On Dec 10, 2015, at 8:45 AM, Adrian Kashivskyy <<a href="mailto:adrian.kashivskyy@me.com" class="">adrian.kashivskyy@me.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=""><blockquote type="cite" class="">What “break" currently does can be unclear. For example, “break” without a label in do {…} doesn’t just break out of the do.<br class=""></blockquote><div class=""><br class=""></div>Because `do` isn't a loop.</div></div></blockquote><div class=""><br class=""></div><div class="">Neither is a case but the “break" behaviour is different.</div><div class=""><br class=""></div><div class="">Moreover, you can give do a label to just break out of the do.</div></div><div class=""><br class=""></div></div></div></blockquote><div><br class=""></div><div><br class=""></div><div>As you just said if you think “break” behavior is unclear, you can add a label.</div><div><br class=""></div><div>It doesn’t seem to be up for debate that labels provide much more clarity than your proposal. To reduce clarity because you find it annoying to come up with label names is not consistent with the design of the language; which clearly favors clarity.</div><div><br class=""></div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""><div class="">
<div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><font color="#929292" class=""><br class="Apple-interchange-newline">Pozdrawiam – Regards,</font></div><div style="font-family: Helvetica; font-size: 12px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class=""><font color="#929292" class="">Adrian Kashivskyy</font></div>
</div>
<br class=""><div class=""><blockquote type="cite" class=""><div class="">Wiadomość napisana przez Amir Michail via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> w dniu 10.12.2015, o godz. 14:28:</div><br class="Apple-interchange-newline"><div class=""><div class=""><br class=""><blockquote type="cite" class="">On Dec 10, 2015, at 8:20 AM, Kevin Wooten <<a href="mailto:kdubb@me.com" class="">kdubb@me.com</a>> wrote:<br class=""><br class="">Curios as to what you see the advantage of this is, over labels? Seems to me it only saves a few keystrokes at the expense of clarity.<br class=""></blockquote><br class="">What “break" currently does can be unclear. For example, “break” without a label in do {…} doesn’t just break out of the do.<br class=""><br class="">Also, I really don’t like coming up with label names. They tend to be uninteresting.<br class=""><br class=""><blockquote type="cite" class=""><br class="">Given the stated goals of Swift I don’t imagine this would be an interesting proposal for many.<br class=""><br class=""><blockquote type="cite" class="">On Dec 10, 2015, at 5:59 AM, Amir Michail via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><br class="">For example:<br class=""><br class="">for* … {<br class="">for** ... {<br class=""> for ... {<br class=""> …<br class=""> if … { break for* }<br class=""> ...<br class=""> if … { continue for** }<br class=""> ...<br class=""> }<br class="">}<br class="">}<br class=""><br class="">repeat {<br class="">do {<br class=""> for … {<br class=""> if … { break do }<br class=""> if … { continue repeat }<br class=""> }<br class=""> …<br class="">}<br class="">} while …<br class=""><br class=""><br class="">_______________________________________________<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=""></blockquote><br class=""></blockquote><br class="">_______________________________________________<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></div></blockquote></div><br class=""></div></div></div></blockquote></div><br class=""></div></div></blockquote></div><br class=""></body></html>