<html><head><meta http-equiv="Content-Type" content="text/html charset=utf-8"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><br class=""><div><blockquote type="cite" class=""><div class="">On Apr 14, 2016, at 3:48 PM, Douglas Gregor <<a href="mailto:dgregor@apple.com" class="">dgregor@apple.com</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><meta http-equiv="Content-Type" content="text/html charset=utf-8" class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class="">Proposal link: <a href="https://github.com/apple/swift-evolution/blob/master/proposals/0062-objc-keypaths.md" class="">https://github.com/apple/swift-evolution/blob/master/proposals/0062-objc-keypaths.md</a></div><div class=""><br class=""></div><div class="">Hello Swift Community,</div><div class=""><br class=""></div><div class="">The review of SE-0062 "Referencing Objective-C key-paths” ran from April 7...12, 2016. The proposal is <b class="">accepted</b>, with one adjustment to the handling of collections: rather than support any SequenceType as a collection, the core team wants a narrower rule for only the primary Cocoa collection types (NSArray, NSDictionary, NSSet) and their Swift-bridged equivalents (Array, Dictionary, Set), due to implementation concerns.</div><div class=""><br class=""></div><div class="">Feedback on this proposal was generally positive, and the proposal fits well with #selector (<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0022-objc-selectors.md" class="">SE-0022</a>). There was some discussion during the review of extending the proposal to more strongly-typed key paths. However, the core team felt that this feature is important for Swift 3 to support the renaming of Objective-C APIs in Swift (<a href="https://github.com/apple/swift-evolution/blob/master/proposals/0005-objective-c-name-translation.md" class="">SE-0005</a>), and that such a significant increase in scope would jeopardize the feature for Swift 3.</div><div class=""><br class=""></div><div class="">We welcome an implementation of this proposal. I’ve filed a ticket at</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>We welcome an implementation of this proposal. I’ve filed a ticket at</div></div></div></blockquote><div><br class=""></div>Paste fail, it’s here:</div><div><br class=""></div><div><span class="Apple-tab-span" style="white-space:pre"> </span><a href="https://bugs.swift.org/browse/SR-1237" class="">https://bugs.swift.org/browse/SR-1237</a></div><div><br class=""><blockquote type="cite" class=""><div class=""><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" class=""><div class=""><br class=""></div><div class="">to track the implementation.</div><div class=""><br class=""></div><div class=""><span class="Apple-tab-span" style="white-space:pre"> </span>- Doug</div><div class=""><br class=""></div></div>_______________________________________________<br class="">swift-evolution-announce mailing list<br class=""><a href="mailto:swift-evolution-announce@swift.org" class="">swift-evolution-announce@swift.org</a><br class="">https://lists.swift.org/mailman/listinfo/swift-evolution-announce<br class=""></div></blockquote></div><br class=""></body></html>