<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 Dec 23, 2015, at 9:03 AM, Nick O'Neill via swift-users <<a href="mailto:swift-users@swift.org" class="">swift-users@swift.org</a>> wrote:</div><br class="Apple-interchange-newline"><div class=""><div style="font-family: Alegreya-Regular; font-size: 15px; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; orphans: auto; text-align: start; text-indent: 0px; text-transform: none; white-space: normal; widows: auto; word-spacing: 0px; -webkit-text-stroke-width: 0px;" class="">Did I miss a spot where I can submit a PR for this or is there a chance the Swift headers for these UIKit APIs could be made open source in the future?</div></div></blockquote></div><br class=""><div class="">As with all things Apple that aren’t open source, the answer is “go to <a href="http://bugreport.apple.com" class="">bugreport.apple.com</a> and file a request”. :/</div><div class=""><br class=""></div><div class="">There are no Swift headers for Objective-C APIs; the Swift API is derived at compile-time by parsing the .h files. Apple’s not going to open-source things like UIKit, even the headers, because the headers reveal all the functionality in the framework. That would impede their ability to work on features in secret and then announce them at WWDC. (Unless they did their work on internal branches … but then merging those on a yearly basis sounds unpleasant!)</div><div class=""><br class=""></div><div class="">For these and other reasons, I think Swift questions relating to UIKit or AppKit or other closed-source Apple frameworks are better addressed on the cocoa-dev mailing list at <a href="http://lists.apple.com" class="">lists.apple.com</a>.</div><div class=""><br class=""></div><div class="">—Jens</div></body></html>