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

Sean Heber sean at fifthace.com
Thu Apr 6 11:31:18 CDT 2017

> On Apr 6, 2017, at 11:19 AM, Douglas Gregor <dgregor at apple.com> wrote:
>> On Apr 6, 2017, at 8:13 AM, Ricardo Parada via swift-evolution <swift-evolution at swift.org> wrote:
>> 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.  
> 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. 

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?

> The core team discussed single quotes, and decided that we want to save them for something in the string/character realm.

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?


More information about the swift-evolution mailing list