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

Fabian Ehrentraud Fabian.Ehrentraud at willhaben.at
Mon Jun 6 01:45:51 CDT 2016


• What is your evaluation of the proposal?
-1 for the current proposal, +1 for being able to mix regular boolean expressions and `let` expressions.

• Is the problem being addressed significant enough to warrant a change to Swift?
Yes, not being able to mix different clause types feels artificial in current Swift.

• Does this proposal fit well with the feel and direction of Swift?
No, semicolons don't read very Swifty.

• 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?
10 minutes


On 27.05.2016, at 21:11, Joe Groff via swift-evolution <swift-evolution at swift.org<mailto: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

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?
• 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?

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<mailto: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/20160606/eaa314d3/attachment.html>


More information about the swift-evolution mailing list