> What is your evaluation of the proposal?
I like it and think it’s something Swift should definitely have.
A quibble: I think there’d be value in also having:
#key(ClassName.propertyName)
…which is the same as `#keyPath`, but without support for *paths*.
It’s functionally-redundant with
> https://github.com/apple/swift-evolution/blob/master/proposals/0062-objc-keypaths.md
> • What is your evaluation of the proposal?
I'm definitely in favor and look forward to using #keyPath. I have one note,
one suggestion and one concern, but even without any of them being addressed, I
Hello Swift community,
The review of SE-0062 “Referencing Objective-C key-paths" begins now and runs
through April 12, 2016. The proposal is available here:
https://github.com/apple/swift-evolution/blob/master/proposals/0062-objc-keypaths.md
Reviews are an important part of the Swift evolution
