Re: [swift-evolution] [Review] SE-0098: Lowercase didSet and willSet for more consistent keyword casing
I agree with Joe, so -1 from me. There’s no hurry to pin down rules for a feature which hasn’t been fully developed. Staying with the existing naming will reduce confusion. And I think camelCase will be the best fit for property behaviours, so this is an unnecessary move. > On 25 May 2016, at 4:07 AM, Chris Lattner via swift-evolution > 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: > > > https://github.com/apple/swift-evolution/blob/master/proposals/0098-didset-capitalization.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. > > 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 > > https://github.com/apple/swift-evolution/blob/master/process.md > > Thank you, > > -Chris Lattner > Review Manager > > > ___ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
Re: [swift-evolution] [Review] SE-0098: Lowercase didSet and willSet for more consistent keyword casing
(comments inline) > Am 24.05.2016 um 20:07 schrieb Chris Lattner via swift-evolution > : > > 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: > > > https://github.com/apple/swift-evolution/blob/master/proposals/0098-didset-capitalization.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. > > 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 . I don't like this. I don't find the consistency arguments convincing. Consistency has to be defined in terms of observable behavior of the language; If a word is a "keyword" or not is an implementation detail of the compiler IMHO(!), so there should be no rule regarding case-ness of keywords. > * Is the problem being addressed significant enough to warrant a change > to Swift? No, I'd rather see progress on static/dynamic dispatch rules of protocol extensions, for example. Changing the case-ness of just two random language keywords doesn't have any influence on the ABI or the API or the semantics of the language. > * Does this proposal fit well with the feel and direction of Swift? Don't think so. > * If you have used other languages or libraries with a similar feature, > how do you feel that this proposal compares to those? ObjC has -willSetValueForKey: and -didSetValueForKey: . It's not the same, because willSet and didSet are not related to KVO. But using the same camelCase syntax for didSet and willSet feels more consistent to me. At least, the semantic distance between didSet and -didSetValueForKey: is less than the semantic distance between didSet and associatedtype. (I compare them because associatedtype is also a keyword, and it's all lowercase.) > * How much effort did you put into your review? A glance, a quick > reading, or an in-depth study? Read the proposal, participated in the discussion. -Michael ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
Re: [swift-evolution] [Review] SE-0098: Lowercase didSet and willSet for more consistent keyword casing
> On May 24, 2016, at 11:07 AM, Chris Lattner via swift-evolution > 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: > > > https://github.com/apple/swift-evolution/blob/master/proposals/0098-didset-capitalization.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. > > 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 bc it doesn't address the fact that property behaviors will have their own naming convention separate from keyboard naming in order to address 2+ word properly names; not to mention syntax changes that will be part of the name signature. >* Is the problem being addressed significant enough to warrant a change to > Swift? No >* Does this proposal fit well with the feel and direction of Swift? No >* If you have used other languages or libraries with a similar feature, > how do you feel that this proposal compares to those? n/a >* How much effort did you put into your review? A glance, a quick reading, > or an in-depth study? Quick study. > > More information about the Swift evolution process is available at > >https://github.com/apple/swift-evolution/blob/master/process.md > > Thank you, > > -Chris Lattner > Review Manager > > > ___ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution ___ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
