<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=""><div class="">The main advantage is not in this change by itself, but in the fact that it tidies up the syntax and makes it easier to support other additive proposals in the future that might make better use of the colon syntax— such as targeted continue statements in `switch` or a `switch` expression syntax. Both could probably be accomplished without this change, but I think they’d be less clean.</div><div class=""><br class=""></div>I guess my argument on familiarity has been that using curly braces is more like the C family of languages in that the Swift `case`s are separate scopes and C/C++ would require curly braces to create those scopes. At the same time the Swift `switch` is different from the C `switch` in that it does not implicitly fall through so a small syntax difference isn’t without justification.<div class=""><br class=""></div><div class=""><br class=""></div><div class="">That said, reactions haven't been overwhelmingly positive, so I’ll let it go unless someone suggests otherwise.</div><div class=""><br class=""></div><div class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Jul 18, 2016, at 16:23 , 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="">On Jul 17, 2016, at 10:07 PM, Jose Cheyo Jimenez via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</a>> wrote:<br class=""><div class=""><blockquote type="cite" class=""><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="">I think this proposal is not <div class=""><br class=""><div class=""><span style="color: rgb(51, 51, 51); font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; font-size: 16px; widows: 1; background-color: rgb(255, 255, 255);" class=""> ""better enough" for it to make sense to diverge from the precedent established by the C family of languages.</span>”</div><div class=""><br class=""></div><div class="">And I think the same would go for this</div><div class=""><br class=""></div><div class="">“<span style="color: rgb(51, 51, 51); font-family: -apple-system, BlinkMacSystemFont, 'Segoe UI', Roboto, Helvetica, Arial, sans-serif, 'Apple Color Emoji', 'Segoe UI Emoji', 'Segoe UI Symbol'; font-size: 16px; widows: 1; background-color: rgb(255, 255, 255);" class="">Swift is designed to feel like a member of the C family of languages. Switching keywords away from C precedent without strong motivation is a non-goal</span>”</div><div class=""><br class=""></div><div class=""><a href="https://github.com/apple/swift-evolution/blob/master/commonly_proposed.md" class="">https://github.com/apple/swift-evolution/blob/master/commonly_proposed.md</a></div><div class=""><br class=""></div><div class="">I just don’t think we gain much by switching to curly braces. </div></div></div></div></blockquote><br class=""></div><div class="">I agree. I don’t think this proposal is worth considering at this point.</div><div class=""><br class=""></div><div class="">-Chris</div><br class=""></div></div></blockquote></div><br class=""></div></body></html>