[swift-evolution] [swift-evolution-announce] [Review] SE-0099: Restructuring Condition Clauses
matthew at anandabits.com
Fri May 27 14:28:38 CDT 2016
> • 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:
condition-separator → ; | \n
condition-list → condition | condition condition-separator condition-list
condition → expression | availability-condition | case-condition | optional-binding-condition
If so, what is the reason for requiring semicolons here when they can be omitted elsewhere in Swift?
> • Is the problem being addressed significant enough to warrant a change to Swift?
> • Does this proposal fit well with the feel and direction of Swift?
> • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
> • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
Participated in the discussion and offered feedback along the way, as well as reading the final proposal.
> More information about the Swift evolution process is available at
> Thank you,
> Review Manager
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
More information about the swift-evolution