<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Thu, Apr 6, 2017 at 9:31 AM Sean Heber via swift-evolution <<a href="mailto:swift-evolution@swift.org">swift-evolution@swift.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br class="gmail_msg">
> On Apr 6, 2017, at 11:19 AM, Douglas Gregor <<a href="mailto:dgregor@apple.com" class="gmail_msg" target="_blank">dgregor@apple.com</a>> wrote:<br class="gmail_msg">
><br class="gmail_msg">
>><br class="gmail_msg">
>> On Apr 6, 2017, at 8:13 AM, Ricardo Parada via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a>> wrote:<br class="gmail_msg">
>><br class="gmail_msg">
>> I agree, there's an analogy between strings and key paths, and in that regards the single quote would make sense. I would not complain.<br class="gmail_msg">
><br class="gmail_msg">
> The only analogy between strings and key-paths is that the existing Cocoa APIs for key-paths use strings. That’s not an analogy to hang language syntax on, because it’s relevance will fade quickly.<br class="gmail_msg">
<br class="gmail_msg">
Why would it fade quickly? Do we expect the concept of keypaths to go away over time? If so, why are we even designing a syntax for keypaths?<br class="gmail_msg"></blockquote><div><br></div><div>I think the naming of this proposal as "keypaths" has caused some confusion in this regard. Try to consider them without the Objective-C history and look at Swift as a language in its own right: does it make sense for a chain of strongly-typed unbound property references—AND unbound method references, because they will use this syntax as well—to be represented as something akin to a string literal? IMO, the answer to that is no.</div><div><br></div><div>Nobody is suggesting that the concept of keypaths will go away—the proposal is evidence of that and in fact it shows that they want to improve them beyond the string-based versions that were required by Objective-C because of its dynamism and string-based-selector syntax.</div><div><br></div><div>It would be a mistake to tie down Swift's superior implementation based on tortured analogies to Objective-C.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br class="gmail_msg">
<br class="gmail_msg">
> The core team discussed single quotes, and decided that we want to save them for something in the string/character realm.<br class="gmail_msg">
<br class="gmail_msg">
Are they to be saved for something specific or is this just because a lot of languages use single quotes for character literals? Why is this association any more sacred than an association with Cocoa string keypaths?<br class="gmail_msg">
<br class="gmail_msg">
l8r<br class="gmail_msg">
Sean<br class="gmail_msg">
<br class="gmail_msg">
_______________________________________________<br class="gmail_msg">
swift-evolution mailing list<br class="gmail_msg">
<a href="mailto:swift-evolution@swift.org" class="gmail_msg" target="_blank">swift-evolution@swift.org</a><br class="gmail_msg">
<a href="https://lists.swift.org/mailman/listinfo/swift-evolution" rel="noreferrer" class="gmail_msg" target="_blank">https://lists.swift.org/mailman/listinfo/swift-evolution</a><br class="gmail_msg">
</blockquote></div></div>