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

Chris Lattner clattner at apple.com
Sat May 28 12:11:24 CDT 2016

On May 27, 2016, at 12:37 PM, Erica Sadun via swift-evolution <swift-evolution at swift.org> 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:

No I didn’t think about or consider it.  I agree with you that this seems like it would be consistent with the rest of the language and can use the same mechanics we use for disambiguating two expressions on consecutive lines in a brace statement.  It also seems like it would lead to more pretty code in general as well.

> 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.
> 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.

I agree that this could be positioned as a subsequent additional proposal.  I’d personally be fine with looping this into the original proposal, but I’m also happy to split it out if you'd prefer Erica,


More information about the swift-evolution mailing list