[swift-evolution] [swift-evolution-announce] [Review] SE-0064: Referencing the Objective-C selector of property getters and setters
sebastian at iosphere.de
Fri Apr 8 07:10:04 CDT 2016
> What is your evaluation of the proposal?
> Is the problem being addressed significant enough to warrant a change to Swift?
Yes. I agree with Michael Buckley that this feels more like an oversight in SE-0022 rather than a completely new thing.
> Does this proposal fit well with the feel and direction of Swift?
Yes. I think it makes sense to use explicit getter/setter parameter names, as opposed to relying on the ObjC-based foo/setFoo: conventions. While the lines between property accessors and methods are blurry in ObjC, they are different things in Swift. I’m aware that this feature requires ObjC under the hood, but that’s not something you need to know when creating a selector.
> If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
Well, ObjC… I’ve explained the difference above.
> How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
I’ve read the proposal and the previous review.
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the swift-evolution