[swift-evolution] [Review] SE-0060: Enforcing order of defaulted parameters
michael.peternell at gmx.at
Wed May 4 12:13:10 CDT 2016
> Am 04.05.2016 um 05:52 schrieb Chris Lattner via swift-evolution <swift-evolution at swift.org>:
> Hello Swift community,
> The review of "SE-0060: Enforcing order of defaulted parameters" begins now and runs through May 9. The proposal is available here:
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at
> or, if you would like to keep your feedback private, directly to the review manager.
> What goes into a review?
> The goal of the review process is to improve the proposal under review through constructive criticism and contribute to 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?
+1 The advantage is that the code becomes easier to understand if everyone uses the same parameter order. The disadvantage is that users don't have as much freedom to re-order the parameters as they like. I think the advantage weighs more. Furthermore, having different parameter orders in the same program could probably give the impression that the parameter order is important. If only one parameter order is possible, there can be no confusion regarding that.
> * 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?
Read the proposal, imagined some friends discussing how the parameters should be ordered for a particular function, and thought "let's remove this trap from the language."
More information about the swift-evolution