[swift-evolution] [swift-evolution-announce] [Review] SE-0098: Lowercase didSet and willSet for more consistent keyword casing
matthew at anandabits.com
Tue May 24 13:38:52 CDT 2016
Sent from my iPad
> On May 24, 2016, at 1:21 PM, Joe Groff via swift-evolution <swift-evolution at swift.org> wrote:
> didSet and willSet are already contextual rather than formal keywords, and there's a conceivable future where didSet and willSet are no longer keywords at all if we run with the "property behaviors" feature again in the future. If we think that's likely, I'm not sure this intermediate churn is really worth it.
+1. If we may introduce property behaviors (I hope we do) the naming of 'didSet' and 'willSet' should match the convention for accessors. As those are user-defined and it is not unreasonable to imaging accessorswithseveralwords in their name, I believe e appropriate convention would be lower camel case. As this is the status quo, I believe it is preliminary to make a change.
If a time comes where we either decide against property behaviors and that these should match the all lowercase convention of keywords, or decide to introduce property behaviors with a convention that accessors should be all lowercase migration could easily provided.
>> On May 24, 2016, at 11:07 AM, Chris Lattner <clattner at apple.com> wrote:
>> Hello Swift community,
>> The review of "SE-0098: Lowercase didSet and willSet for more consistent keyword casing" begins now and runs through May 30. 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?
>> * 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
>> Thank you,
>> -Chris Lattner
>> Review Manager
>> swift-evolution-announce mailing list
>> swift-evolution-announce at swift.org
> swift-evolution mailing list
> swift-evolution at swift.org
More information about the swift-evolution