[swift-evolution] [Review] SE-0161: Smart KeyPaths: Better Key-Value Coding for Swift

[James Berry]

> On Apr 3, 2017, at 8:27 AM, James Berry <jberry at rogueorbit.com> wrote:
> 
> On balance, I’m +1 on this proposal, with caveats below…
> 
> I’ve expressed, I don’t really like the #keyPath(Foo, .bar.baz) syntax, because I feel it is confusing to differentiate from the more natural #keyPath(Foo.bar.baz) legacy syntax. I really wish there were a good alternative, and would support renaming the legacy syntax to #objcKeyPath(Foo.bar.baz) and claiming #keyPath for swift key paths, or finding another more seamless way for the compiler to grok the usage intent such that the objc usage can be intuited and special cased.
> 
> James
> 
> 
>> On Mar 30, 2017, at 9:25 AM, Douglas Gregor via swift-evolution <swift-evolution at swift.org <mailto:swift-evolution at swift.org>> wrote:
>> 
>> Hello Swift community,
>> 
>> The review of SE-0161 "Smart KeyPaths: Better Key-Value Coding for Swift" begins now and runs through April 5, 2017. The proposal is available here:
>> 
>> https://github.com/apple/swift-evolution/blob/master/proposals/0161-key-paths.md <https://github.com/apple/swift-evolution/blob/master/proposals/0161-key-paths.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>
> 
> 
> 
>> What is your evaluation of the proposal?
> Overall very positive, with cautions on the syntax.
> 
>> Is the problem being addressed significant enough to warrant a change to Swift?
> Yes
> 
>> Does this proposal fit well with the feel and direction of Swift?
> Yes
> 
>> If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?
> Java, objc.
> 
>> How much effort did you put into your review? A glance, a quick reading, or an in-depth study?
> Thorough.
> 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.swift.org/pipermail/swift-evolution/attachments/20170403/5ddba470/attachment.html>