Thanks for the feedback Jens,
I understand the concept of deriving the Swift API from the Objective-C
headers (nullability annotations and all...) but I was under the impression
that some of the more Swifty initializers were accomplished with
convenience initializers in small extensions written in Swift.
While I'm not certain that difficulty with git would make this entirely
infeasible, I do see your point about making things a little more difficult
around WWDC time. I'll see what cocoa-dev has to say about it.
On Wed, Dec 23, 2015 at 9:34 AM, Jens Alfke <firstname.lastname@example.org> wrote:
On Dec 23, 2015, at 9:03 AM, Nick O'Neill via swift-users < > email@example.com> wrote:
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
As with all things Apple that aren’t open source, the answer is “go to
bugreport.apple.com and file a request”.
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
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 lists.apple.com.