<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 Jun 16, 2016, at 3:57 PM, David Hart via swift-evolution <<a href="mailto:swift-evolution@swift.org" class="">swift-evolution@swift.org</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="">I’ve only started using the transformed APIs from Apple frameworks that were auto-modified and I’ve found a few cases where the automatic translation doesn’t seem to follow the Swift Design Guidelines. I don’t know how much can be fixed manually, but if it can, it would be forth congregating as a community to prepare a massive list of proportions before the new APIs are set in stone in the fall.</div></div></blockquote><br class=""></div><div>Hi David,</div><div><br class=""></div><div>swift-evolution isn’t the right process for proposing changes to Apple frameworks, but you raise good points, and I really value the feedback. </div><div><br class=""></div><div>If you file a radar with <a href="http://bugreporter.apple.com" class="">bugreporter.apple.com</a> and let us know the radar #, we will be happy to escalate this with the team in question. Thank you!</div><div><br class=""></div><div>-Chris</div><br class=""></body></html>