[swift-evolution] Modernize Switch/Case Statements?

[Haravikk]

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.

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.

> On 29 Jan 2016, at 22:45, Rudolf Adamkovič via swift-evolution <swift-evolution at swift.org> wrote:
> 
> +2 from me! One for curly braces and one for proper indentation.
> 
> R+
> 
>> On 28 Jan 2016, at 02:35, Joseph Essin via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 
>> As a budding iOS developer, I thought it might be nice if Swift were to further improve on C's switch 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.
>> 
>> Here's a quick example of what it might be.
>> 
>> switch value {
>>   case expression {
>>   }
>> }
>> 
>> I apologize if this message isn't in the right format--I've not used a mailing list before.
>> 
>> Joseph Essin
>> _______________________________________________
>> swift-evolution mailing list
>> swift-evolution at swift.org <mailto:swift-evolution at swift.org>
>> https://lists.swift.org/mailman/listinfo/swift-evolution
> 
> _______________________________________________
> swift-evolution mailing list
> swift-evolution at swift.org
> https://lists.swift.org/mailman/listinfo/swift-evolution

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160130/3d8cb0d3/attachment.html>