[swift-evolution] [swift-evolution-announce] [Review] SE-0099: Restructuring Condition Clauses

[Matthew Johnson]

> On May 27, 2016, at 2:37 PM, Erica Sadun <erica at ericasadun.com> wrote:
> 
> 
>> On May 27, 2016, at 1:28 PM, Matthew Johnson via swift-evolution <swift-evolution at swift.org> wrote:
>> 
>>> 	• What is your evaluation of the proposal?
>> 
>> +1.  I believe it improves the clarity of condition clauses and as the proposal suggests, I think it will make it easier for programmers to learn and understand what is possible with them.
>> 
>> Did you consider allowing the semicolon to be omitted when a newline separates conditions?  Something like this:
> 
> Given the whole newline groundswell that has emerged on SE, I did consider it but when I mocked up examples, it felt less readable and I suspect it would negatively affect the clarity of parsing this proposal aims to introduce.

Maybe Joe can comment on the parsing question.

What kinds of examples did you look at where you felt that way?  IMO the example in the proposal reads better without the semicolons:

guard
    x == 0;
    let y = optional;
    z == 2 
    else { ... }

vs

guard
    x == 0
    let y = optional
    z == 2 
    else { ... }


> 
> I'd really like to see a separate newline-as-separator proposal brought forward and formally reviewed. It's garnered a few very vocal supporters but it really doesn't fall under the umbrella of this proposal. I'd like the matter to be settled one way or the other for the sake of closure.

The other discussion has been about introducing newline-as-separator for comma separated lists.  

I raised the question in my review because Swift already uses newline-as-separator for semicolon separated lists (statements).

-Matthew

> 
> -- Erica
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20160527/8aa35fe2/attachment.html>