> On Apr 6, 2017, at 11:01 AM, Brad Hilton <[email protected]> wrote:
>
> -1. Not a huge fan of the back slash. Doesn’t make sense considering we can
> refer to unapplied method references without the backslash. Maybe we can
> settle on some unified syntax for both? How about Person.name.get /
> Person.name.set for getter/setter references.
Did you read the core team’s commentary on unapplied method references?
https://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000342.html<https://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000342.html>
<https://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000342.html%3Chttps://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000342.html%3E>
?
- Doug
>
>> Hello Swift community,
>>
>> The second review of SE-0161 "Smart KeyPaths: Better Key-Value Coding for
>> Swift" begins now and runs through April 9, 2017. The revised 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>
>> The core team’s feedback from the first review of this proposal can be
>> viewed at:
>>
>> https://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000342.html<https://lists.swift.org/pipermail/swift-evolution-announce/2017-April/000342.html>
>> 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. When replying, please try to keep the proposal link at the top of
>> the message:
>>
>> Proposal link:
>>
>> 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>
>> Reply text
>> Other replies
>> <https://github.com/apple/swift-evolution/pulls#what-goes-into-a-review-1>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 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,
>>
>> -Doug
>>
>> Review Manager
>>
>>
_______________________________________________
swift-evolution mailing list
[email protected]
https://lists.swift.org/mailman/listinfo/swift-evolution
