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

L Mihalkovic laurent.mihalkovic at gmail.com
Fri May 27 14:53:48 CDT 2016

> On May 27, 2016, at 9:11 PM, Joe Groff via swift-evolution <swift-evolution at swift.org> wrote:
> Hello Swift community,
> The review of SE-0099 “Restructuring Condition Clauses” begins now and runs through June 3, 2016. The proposal is available here:
> 	https://github.com/apple/swift-evolution/blob/master/proposals/0099-conditionclauses.md <https://github.com/apple/swift-evolution/blob/master/proposals/0099-conditionclauses.md>
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> 	https://lists.swift.org/mailman/listinfo/swift-evolution
> or, if you would like to keep your feedback private, directly to the review manager. When replying, please try to keep the proposal link at the top of the message:
> 	Proposal link:
> 		https://github.com/apple/swift-evolution/blob/master/proposals/0099-conditionclauses.md
> 	Reply text
> 	Other replies
> What goes into a review?
> The goal of the review process is to improve the proposal under review through constructive criticism and, eventually, determine the direction of Swift. When writing your review, here are some questions you might want to answer in your review:
> 	• What is your evaluation of the proposal?


> 	• Is the problem being addressed significant enough to warrant a change to Swift?

yes. anything to avoid series of cascading guard statements will help push people in the direction of before/after where the safety is verified before proceeding further into a function

> 	• Does this proposal fit well with the feel and direction of Swift?

guard is an essential tool of idiomatic Swift. making it more fluid feels like it removes the right road-blocks

> 	• If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?

using a “;” between successive conditions lists bares a resemblance with how conditions are structured in the Golang IF statement 
if err := dec.Decode(&val); err != nil {
    // ERR has been bound and validated to be NOT nil
this is one of my favorite features of the language

> 	• How much effort did you put into your review? A glance, a quick reading, or an in-depth study?

followed the discussions and understanding the pre-existing limitations this change will lift

> More information about the Swift evolution process is available at
> 	https://github.com/apple/swift-evolution/blob/master/process.md
> Thank you,
> -Joe
> Review Manager
> _______________________________________________
> 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/20160527/7864292f/attachment.html>

More information about the swift-evolution mailing list