> 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 the more-general #keyPath but makes intent clearer, and is IMHO both shorter and clearer at any call-site that require keys, not key-paths. > Is the problem being addressed significant enough to warrant a change to > Swift? Yes for the same reasons #selector was added. > Does this proposal fit well with the feel and direction of Swift? Yes. > 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? Quick read, didn’t follow the lead-up discussion. > 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 Gregor > > Review Manager > > _______________________________________________ > swift-evolution mailing list > swift-evolution@swift.org > https://lists.swift.org/mailman/listinfo/swift-evolution
_______________________________________________ swift-evolution mailing list swift-evolution@swift.org https://lists.swift.org/mailman/listinfo/swift-evolution
