[swift-evolution] [swift-evolution-announce] [Review] SE-0018 Flexible Memberwise Initialization
pierre at monod-broca.fr
Sat Jan 9 04:25:02 CST 2016
* What is your evaluation of the proposal?
* Is the problem being addressed significant enough to warrant a change to Swift?
Yes, the current feature is frustrating. Most notably when:
- some stored properties have default values
- you want to change the access level of the member-wise init
* Does this proposal fit well with the feel and direction of Swift?
I think so. It avoids most boilerplate while staying pretty clear to read.
I see one downside with the chosen syntax: I'm concerned the "..." placeholder might be confusing sometimes.
* If you have you 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?
I read carefully the latest version of the proposal. I partly read the discussion thread.
> Le 6 janv. 2016 à 19:13, Chris Lattner <clattner at apple.com> a écrit :
> Hello Swift community,
> The review of "Flexible Memberwise Initialization" begins now and runs through January 10th. The proposal is available here:
> https://github.com/apple/swift-evolution/blob/master/proposals/0018-flexible-memberwise-initialization.md <https://github.com/apple/swift-evolution/blob/master/proposals/0019-package-manager-testing.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 <https://lists.swift.org/mailman/listinfo/swift-evolution>
> 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, 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 you 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 <https://github.com/apple/swift-evolution/blob/master/process.md>
> Thank you,
> Review Manager
> swift-evolution-announce mailing list
> swift-evolution-announce at swift.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution