<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="">I agree on the break and fallthrough points, I also think forcing curly braces would add unwanted complexity to simple switch blocks. Even worse - the way switch looks today it encourages clean and simple blocks, with short cases; adding curly braces might lead to huge switch cases which are impossible to follow…<div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jan 30, 2016, at 2:03 PM, Andrew Bennett via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class="">I like this idea, but I don't have enough detail to +1.<div class=""><br class=""></div><div class="">It would be good to show how all current switch behaviour would work.</div><div class=""><br class=""></div><div class="">How would 'break' and 'fallthrough' work?</div><div class=""><br class=""></div><div class="">It seems 'break' is redundant now.</div><div class=""><br class=""></div><div class="">Would the following code's 'break' act on the switch, or on the for loop?</div><div class=""><br class=""></div><div class="">for i in 0...5 {</div><div class=""> switch i {</div><div class=""> case 4 { break }</div><div class=""> default { print(i) }</div><div class=""> }</div><div class="">}</div><div class=""><br class="">On Saturday, 30 January 2016, Haravikk via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div style="word-wrap:break-word" class=""><div class="">I’d say to make it optional, as the use of just a colon is great for compact switch statements with short cases, so I think they’re worth retaining.</div><div class=""><br class=""></div><div class="">Actually, one thing we don’t have in Swift is the ability to just put blocks (curly braces) wherever we like, which in some languages is a useful tool for variable scope when you know you only need something for a short time, but might want to re-use the name. Currently they just result in a “trailing closure separated by multiple new-lines” warning, so they could perhaps be made available, in which event you could use them in larger case statements whenever you wished.</div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 29 Jan 2016, at 22:45, Rudolf Adamkovič via swift-evolution <<a href="javascript:_e(%7B%7D,'cvml','swift-evolution@swift.org');" target="_blank" class="">swift-evolution@swift.org</a>> wrote:</div><br class=""><div class=""><div style="word-wrap:break-word" class=""><div class="">+2 from me! One for curly braces and one for proper indentation.</div><div class=""><br class=""></div><div class="">R+</div><br class=""><div class=""><blockquote type="cite" class=""><div class="">On 28 Jan 2016, at 02:35, Joseph Essin via swift-evolution <<a href="javascript:_e(%7B%7D,'cvml','swift-evolution@swift.org');" target="_blank" class="">swift-evolution@swift.org</a>> wrote:</div><br class=""><div class=""><div dir="ltr" class="">As a budding iOS developer, I thought it might be nice if Swift were to further improve on C's <i class="">switch</i> statement by using curly brackets to denote a block instead of a colon. It seems like this would be more consistent with the language at large and make indention more intuitive.<div class=""><br class=""></div><div class="">Here's a quick example of what it might be.</div><div class=""><span style="font-size:12.8px" class=""><br class=""></span></div><div class=""><span style="font-size:12.8px" class="">switch </span><i style="font-size:12.8px" class="">value</i><span style="font-size:12.8px" class=""> </span><span style="font-size:12.8px" class="">{</span><br class=""></div><div class=""><div style="font-size:12.8px" class=""> case <i class="">expression</i> {</div><div style="font-size:12.8px" class=""> }</div><div style="font-size:12.8px" class="">}</div></div><div style="font-size:12.8px" class=""><br class=""></div><div style="font-size:12.8px" class="">I apologize if this message isn't in the right format--I've not used a mailing list before.</div><div style="font-size:12.8px" class=""><br class=""></div><div style="font-size:12.8px" class="">Joseph Essin</div></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="javascript:_e(%7B%7D,'cvml','swift-evolution@swift.org');" target="_blank" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div>_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="javascript:_e(%7B%7D,'cvml','swift-evolution@swift.org');" target="_blank" class="">swift-evolution@swift.org</a><br class=""><a href="https://lists.swift.org/mailman/listinfo/swift-evolution" target="_blank" class="">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class=""></div></blockquote></div><br class=""></div></blockquote></div>
_______________________________________________<br class="">swift-evolution mailing list<br class=""><a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution<br class=""></div></blockquote></div><br class=""></div></body></html>