<div dir="ltr"><div style="min-height:100%"><div class="gmail-nH" style="width:1920px"><div class="gmail-nH" style=""><div class="gmail-nH gmail-bkL"><div class="gmail-no"><div class="gmail-nH gmail-bkK gmail-nn" style="width:1718px"><div class="gmail-nH"><div class="gmail-nH"><div class="gmail-nH gmail-ar4 gmail-B"><div class="gmail-aeI"><div class="gmail-AO"><div id="gmail-:4" class="gmail-Tm gmail-aeJ" style="height:891px"><div id="gmail-:2" class="gmail-aeF" style="min-height:459px"><div class="gmail-nH"><div class="gmail-nH"><div class="gmail-nH gmail-g"><table class="gmail-Bs gmail-nH gmail-iY" cellpadding="0" style="width:1688px"><tbody><tr><td class="gmail-Bu"><div class="gmail-nH gmail-if"><div class="gmail-nH gmail-aHU"><div class="gmail-nH gmail-hx"><div class="gmail-nH"><div class="gmail-h7" tabindex="-1"><div class="gmail-Bk" style="width:1437px"><div class="gmail-G3 gmail-G2"><div id="gmail-:3n5"><div class="gmail-adn gmail-ads" style="padding-bottom:20px"><div class="gmail-gs"><div id="gmail-:3jw" class="gmail-ii gmail-gt gmail-adP gmail-adO" style="font-size:12.8px"><div id="gmail-:3o2" class="gmail-a3s gmail-aXjCH gmail-m15b20d5da76ef89d"><div style="word-wrap:break-word"><span class="gmail-im"><blockquote type="cite" style="font-size:12.8px"><div style="word-wrap:break-word"><ul style="box-sizing:border-box;padding-left:2em;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,blinkmacsystemfont,"segoe ui",helvetica,arial,sans-serif,"apple color emoji","segoe ui emoji","segoe ui symbol";font-size:16px"><li style="box-sizing:border-box">What is your evaluation of the proposal?</li></ul></div></blockquote></span><div>+1</div><span class="gmail-im"><br><blockquote type="cite"><div style="word-wrap:break-word"><ul style="box-sizing:border-box;padding-left:2em;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,blinkmacsystemfont,"segoe ui",helvetica,arial,sans-serif,"apple color emoji","segoe ui emoji","segoe ui symbol";font-size:16px"><li style="box-sizing:border-box;margin-top:0.25em">Is the problem being addressed significant enough to warrant a change to Swift?</li></ul></div></blockquote></span><div>Yes</div><span class="gmail-im"><br><blockquote type="cite"><div style="word-wrap:break-word"><ul style="box-sizing:border-box;padding-left:2em;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,blinkmacsystemfont,"segoe ui",helvetica,arial,sans-serif,"apple color emoji","segoe ui emoji","segoe ui symbol";font-size:16px"><li style="box-sizing:border-box;margin-top:0.25em">Does this proposal fit well with the feel and direction of Swift?</li></ul></div></blockquote></span><div>Yes</div><span class="gmail-im"><br><blockquote type="cite"><div style="word-wrap:break-word"><ul style="box-sizing:border-box;padding-left:2em;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,blinkmacsystemfont,"segoe ui",helvetica,arial,sans-serif,"apple color emoji","segoe ui emoji","segoe ui symbol";font-size:16px"><li style="box-sizing:border-box;margin-top:0.25em">If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?</li></ul></div></blockquote></span><div>I do not have significant experience with this feature in other languages</div><span class="gmail-im"><div><br></div><blockquote type="cite"><div style="word-wrap:break-word"><ul style="box-sizing:border-box;padding-left:2em;margin-top:0px;margin-bottom:16px;color:rgb(36,41,46);font-family:-apple-system,blinkmacsystemfont,"segoe ui",helvetica,arial,sans-serif,"apple color emoji","segoe ui emoji","segoe ui symbol";font-size:16px"><li style="box-sizing:border-box;margin-top:0.25em">How much effort did you put into your review? A glance, a quick reading, or an in-depth study?</li></ul></div></blockquote></span><div>A quick reading.</div></div></div></div></div></div></div></div></div></div></div></div></div></div></td></tr></tbody></table></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div><div class="gmail_extra"><br><div class="gmail_quote">On 31 March 2017 at 11:50, Rien via swift-evolution <span dir="ltr"><<a href="mailto:swift-evolution@swift.org" target="_blank">swift-evolution@swift.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">> • What is your evaluation of the proposal?<br>
<br>
+1<br>
<br>
<br>
> • Is the problem being addressed significant enough to warrant a change to Swift?<br>
<br>
I do not see this as a problem, but as added functionality that would be beneficial<br>
<br>
<br>
> • Does this proposal fit well with the feel and direction of Swift?<br>
<br>
100%<br>
<br>
<br>
> • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
<br>
Yes, but this is actually better due to type safety<br>
<br>
<br>
> • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
<br>
Quick reading.<br>
<br>
<br>
One observation though: I feel that “PartialKeyPath” does not add information, “partial” leaves one swimming: "what exactly is partial?”.<br>
“RootKeyPath” would be more expressive imo. If RootKeyPath would be unacceptable, I would still prefer “RelativeKeyPath” over “PartialKeyPath”.<br>
<br>
Regards,<br>
Rien<br>
<br>
Site: <a href="http://balancingrock.nl" rel="noreferrer" target="_blank">http://balancingrock.nl</a><br>
Blog: <a href="http://swiftrien.blogspot.com" rel="noreferrer" target="_blank">http://swiftrien.blogspot.com</a><br>
Github: <a href="http://github.com/Balancingrock" rel="noreferrer" target="_blank">http://github.com/<wbr>Balancingrock</a><br>
Project: <a href="http://swiftfire.nl" rel="noreferrer" target="_blank">http://swiftfire.nl</a><br>
<span class="im HOEnZb"><br>
<br>
<br>
<br>
<br>
> On 30 Mar 2017, at 18:25, Douglas Gregor via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br>
><br>
</span><div class="HOEnZb"><div class="h5">> Hello Swift community,<br>
><br>
> 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:<br>
><br>
> <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0161-key-paths.md" rel="noreferrer" target="_blank">https://github.com/apple/<wbr>swift-evolution/blob/master/<wbr>proposals/0161-key-paths.md</a><br>
> Reviews are an important part of the Swift evolution process. All reviews should be sent to the swift-evolution mailing list at<br>
><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
> 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:<br>
><br>
> Proposal link:<br>
><br>
> <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0161-key-paths.md" rel="noreferrer" target="_blank">https://github.com/apple/<wbr>swift-evolution/blob/master/<wbr>proposals/0161-key-paths.md</a><br>
> Reply text<br>
> Other replies<br>
> What goes into a review?<br>
><br>
> 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:<br>
><br>
> • What is your evaluation of the proposal?<br>
> • Is the problem being addressed significant enough to warrant a change to Swift?<br>
> • Does this proposal fit well with the feel and direction of Swift?<br>
> • If you have used other languages or libraries with a similar feature, how do you feel that this proposal compares to those?<br>
> • How much effort did you put into your review? A glance, a quick reading, or an in-depth study?<br>
> More information about the Swift evolution process is available at<br>
><br>
> <a href="https://github.com/apple/swift-evolution/blob/master/process.md" rel="noreferrer" target="_blank">https://github.com/apple/<wbr>swift-evolution/blob/master/<wbr>process.md</a><br>
> Thank you,<br>
><br>
> -Doug<br>
><br>
> Review Manager<br>
><br>
</div></div><div class="HOEnZb"><div class="h5">> ______________________________<wbr>_________________<br>
> swift-evolution mailing list<br>
> <a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
> <a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
<br>
______________________________<wbr>_________________<br>
swift-evolution mailing list<br>
<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a><br>
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" target="_blank">https://lists.swift.org/<wbr>mailman/listinfo/swift-<wbr>evolution</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><font color="#999999" size="2" face="georgia, serif"><i>Pranshu Goyal</i></font><div><font color="#999999" size="2" face="times new roman, serif"><i>iOS Developer</i></font></div><div><font color="#999999" size="2" face="times new roman, serif"><i>tlkn</i></font></div></div></div>
</div>